pegasus/README.html - diff

Return to README.html CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/README.html between version 1.1 and 1.6

version 1.1, 2007/01/05 19:46:56

version 1.6, 2009/01/13 18:27:33

Line 1

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

<html>

<head>

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

<title>OpenPegasus 2.6 README</title>

<style>

href="http://www.opengroup.org/stylesheets/info1+margins.css">

<!--

table.MsoNormalTable

{mso-style-parent:"";

font-size:10.0pt;

font-family:"Times New Roman"}

-->

</style>

</head>

<body>

<hr>

Abstract:  Installation, build, and operation

Abstract:  Installation, build,

and operation

information on

the OpenPegasus Version 2.6.0

the OpenPegasus Version 2.8.0

Release. Note that if this readme

conflicts with the documentation in the release notes or interface

definition documents for a particular release, those documents should

Line 22

Line 28

overview to act as an

introduction to OpenPegasus.

<hr>

OpenPegasus - A Manageability

OpenPegasus

- A Manageability

Services Broker for the DMTF CIM/WBEM Standards

Tagline: OpenPegasus is an object manager for

Tagline: OpenPegasus is

an object manager for

DMTF CIM objects written in C++

and hosted by The Open Group

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

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

<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a href="#avail_of_peg">Availability</a>

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

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

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

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

Line 38

Line 45

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

</blockquote>

<a href="#inst_peg">Installing OpenPegasus</a>

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

<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"><a href="#download">Download or Checkout</a>

href="#download">Download or Checkout</a>

<a href="#vfy_req_sw">Verify Dependencies</a>

<a href="#set_envt_var">Set the Environment Variables</a>

<a href="#bld_peg">Build the Executables</a>

Line 49

Line 55

about Building on Linux</a>

<a href="#bld_peg_win">Notes about Building

on Windows</a>

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

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

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

</blockquote>

<a href="#note_bld_peg_ssl">Notes about

Building with SSL</a>

</blockquote>

<a href="#test">Testing an OpenPegasus installation</a>

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

<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a href="#test_icu">Testing with ICU enabled</a>

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

</blockquote>

<hr>

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

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

<div style="margin-left: 40px;">OpenPegasus (also referred to

</h1>

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

<div style="margin-left: 40px;">OpenPegasus (also

referred to

as Pegasus) is an open-source CIM Server for DMTF

CIM objects.

It is

written

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

Line 75

Line 83

exceptions

noted in the documentation.

OpenPegasus includes components for:

OpenPegasus includes

components for:

</div>

<li>A DMTF compliant CIM Server that processes CIM operations, CIM

<li>A DMTF compliant CIM Server 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

<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, CIM Server

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

Server

test functions,

and administrative

functions.</li>

<li>More complete information on the exact functions

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

and their functional state is available from the Release Notes

OpenPegasus release, and at the OpenPegasus <a

(pegasus/ReleaseNotes.htm) and the OpenPegasus <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=799">Feature

href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&ggid=799">Feature

Status Page</a>.</li>

</ol>

<div style="margin-left: 40px;">OpenPegasus is open source and is

</blockquote>

<div style="margin-left: 40px;">OpenPegasus is open source

and is

covered under the MIT open-source

license.

</div>

OpenPegasus is being developed and

OpenPegasus is being

developed and

maintained under the auspices of

The

Open

Group.  OpenPegasus is maintained under the license defined in the

Group.  OpenPegasus is maintained under the license defined in

the

doc

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

directory of this release.  The specific file is: pegasus/doc/license.txt.

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

More information on this

project, access

to the CVS, and

documentation<span

documentation

style="text-decoration: line-through;"> is available

is available

from the Ope<span

from the OpenPegasus

style="text-decoration: line-through;">nPegasus web

web

site.

<a target="blank"

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

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

Note

that all references in this readme to files in the OpenPegasus source

tree are of the form pegasus/..., where "pegasus" is the top-level

directory and also the name of the OpenPegasus module in CVS.

directory and also the name of the OpenPegasus module in the Pegasus

CVS

repository. There are also  other CVS modules for the

OpenPegasus Java client (pegasus-JavaCIMClient)

and for unsupported components and utilities for Pegasus that may be

checked out

separately.  You can use

<a href="http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/">viewCVS</a>

to view the

Pegasus CVS tree

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

<div style="margin-left: 40px;">OpenPegasus is distributed as open

<div style="margin-left: 40px;">OpenPegasus is distributed

as open

source under the MIT open-source

license. The distribution is available via CVS, and as snapshot images

Line 141

Line 167

OpenPegasus can be obtained via any of the following:

<ol>

<li>Released tarballs (see <a

<li>Released tarballs (see <a href="http://www.openpegasus.org/page.tpl?CALLER=page.tpl&ggid=392">ZIP/GZ/EXE

href="http://www.openpegasus.org/page.tpl?CALLER=page.tpl&ggid=392">ZIP/GZ/EXE

link for this release</a>)</li>

<li>CVS (See <a

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

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

code repository</a> for

more information)</li>

<li>Linux RPMs

(see <a

(see <a href="http://www.openpegasus.org/page.tpl?CALLER=page.tpl&ggid=392">RPM

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

link for this release</a>)</li>

</ol>

<font

CVS

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

write accounts are managed by Martin Kirk of The Open Group

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

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

OpenPegasus is regularly tested against a

OpenPegasus is regularly

tested against a

variety of platforms by the

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

development group.  The results of the nightly tests can be

here on our <a

found

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

here on our <a href="http://cvs.opengroup.org/cgi-bin/pegasus-build-status.cgi">Nightly

Build and Test Status</a> page.  The Release Notes provide

Build and Test Status</a> page.  The Release Notes

additional details

(pegasus/ReleaseNotes.htm) provide additional details

regarding the platforms. 

regarding the platforms for the current release.

PEP 287 contains the Release Notes for the 2.6.0 release.

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

We have worked to minimize the dependence of OpenPegasus on other

software

packages and tools. Currently OpenPegasus has the following

dependencies:

dependencies. Note that all of the dependencis listed below are

required only if selected options are enabled except for GNUMAKE which

is the required make tool:

<li>GNUMAKE - To simplify the building of OpenPegasus across

<li>GNUMAKE - To simplify the building of

OpenPegasus across

multiple platforms we

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

using GNUMAKE 3.79.1 successfully both in Windows and Linux

environments. It is available from <a href="http://www.gnu.org">http://www.gnu.org</a>.

</li>

The windows version  of GNUMAKE is available on the Pegasus

<li>FLEX and BISON - These tools were used to develop

web site <a href="http://www.openpegasus.org/pb/protected/index.tpl?CALLER=index.tpl">

the

tools page</a>.</li>

MOF

<li>FLEX and BISON -

compiler and WQL

These tools were used to develop the MOF

parser.  These tools are

compiler and WQL and CQL parsers.  These tools are required ONLY

required only for

for

development of the parsers, not for building OpenPegasus.</li>

development of the parsers, not for building OpenPegasus. 

<li>DOC++ - The OpenPegasus documentation is taken from a

Bison

combination of text files

version 2.3 or later and flex version 2.5.4 or later are required.</li>

and header files themselves. This documentation is

<li>Doxygen - The OpenPegasus documentation

formatted with DOC++ and GAWK.   <font

is taken from a combination of text files and header files themselves.

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

This documentation is formatted with Doxygen and GAWK.  This

is required ONLY if you want to build documentation

from the source tree.  These tools are required to

build the

interface documentation set. </li>

<li>ICU Internationalization libraries - These libraries are

<li>ICU Internationalization libraries -

These libraries are

used as the basis for message catalogs for message

internationalization. See the ICU website

(<a href="http://icu.sourceforge.net/">http://icu.sourceforge.net</a>)

for more information on these

libraries.

libraries. These

libraries are used ONLY if you set the requisite environment variable (

PEGASUS_HAS_ICU) to use ICU

</li>

<li>OpenSSL - If it

<li>OpenSSL

- If it

is intended to use SSL on the

communication protocol, the OpenSSL libraries are required (<a

communication protocol, the OpenSSL libraries are required (<a href="http://www.openssl.org">http://www.openssl.org</a>).</li>

href="http://www.openssl.org">http://www.openssl.org</a>).</li>

<li>OpenSLP

<li>OpenSLP - If you choose

- If you choose

to use

OpenSLP as your choice of SLP implementations, then it will need to be

installed and available to OpenPegasus. Refer to the

PEGASUS_USE_OPENSLP and PEGASUS_OPENSLP_HOME build variables in PEP

PEGASUS_USE_OPENSLP and PEGASUS_OPENSLP_HOME build variables in the

277, and the OpenSLP web site (<a href="http://www.openslp.org">http://www.openslp.org</a>).</li>

doc/BuildAndReleaseOptions.html file, and the OpenSLP web site (<a href="http://www.openslp.org">http://www.openslp.org</a>).</li>

<li>zlib - If you choose to

<li>zlib

- If you choose to

enable the compressed repository feature with the

PEGASUS_ENABLE_COMPRESSED_REPOSITORY build variable, you will need to

install the gzip (GNU zip) compression utility. Refer to

readme.compressed_repository in OpenPegasus source tree, and the gzip

web site (<a style="color: rgb(204, 51, 204);"

web site (<a style="color: rgb(204, 51, 204);" href="http://www.gzip.org">http://www.gzip.org</a>).</li>

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

<li>sqlite

</li>

- If you choose to enable the use of sqlite for the repository, refer

to the doc/BuildAndReleaseOptions.html file for the defintion of the

build variables and the sqlite implementation which may be obtained

either as part of a standard distribution or from <a href="http://www.sqlite.org">http://www.sqlite.org</a>.</li>

</ol>

NOTE:

A set of the required

tools for building on the Windows platform is available on the

OpenPegasus <a

OpenPegasus <a href="http://www.openpegasus.org/pb/index.tpl?CALLER=index.tpl">Tools</a>

href="http://www.openpegasus.org/pb/index.tpl?CALLER=index.tpl">Tools</a>

web page.

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

Pegasus includes the server which can be controlled from the command

line and a

set of clients that provide adminstrative functions

The manpages for each of the commands are in the pegasus/rpm/manLinux/

directory (from CVS).

To see simple help for each command,

To see simple help for each

command,

invoke it with the "--help" option.

<div style="margin-left: 40px;"><span

<div style="margin-left: 40px;">Some of

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

style="font-weight: bold;" class="norm"><span

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

class="norm">Some of

the basic commands:

</div>

<ul>

<li>cimserver (Start the server

<li>cimserver

(Start the server

cimserver)</li>

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

<li>cimserver

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

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

<li>cimserver

traceLevel=4 traceComponents=ALL

(Starts server

with

config flags)</li>

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

</ul>

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

<ul>

<li>cimprovider

-l -s  (Lists providers and their

status)</li>

<li>cimprovider

-e -m OperatingSystemModule

(Enables the

OperatingSystem provider)</li>

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

<li>cimuser

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

-a -u guest _w <ThePassword> (Adds

the user guest

with specified password)

</li>

<li>cimuser -l  (Lists the users )</li>

<li>cimuser

<li>cimconfig -l -c (Lists the

-l  (Lists the users )</li>

<li>cimconfig

-l -c (Lists the

current config options and their current values)

</li>

</ul>

<div style="margin-left: 40px;">NOTE:

<div style="margin-left: 40px;">NOTES:

</div>

<li>Refer to the admin guide in pegasus/doc/Admin_Guide_Release.pdf

<li>Refer to the admin guide in

pegasus/doc/Admin_Guide_Release.pdf

for

more information about administering the OpenPegasus CIM Server.</li>

<li>There are some differences between Windows and other

<li>There are differences between Windows and other

platforms in

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

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

platforms use

the OpenPegasus daemon

configuration option to start the CIM Server as a daemon, on

Line 284

Line 336

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

explains the

exact format of the start and stop options.</li>

<li>The cimuser command is used to manage OpenPegasus users only when

<li>The cimuser command is used to manage OpenPegasus users

only when

the CIM Server is compiled without the PEGASUS_PAM_AUTHENTICATION

environment variable defined. See PEP

environment variable defined. See <a href="http://www.openpegasus.org/pp/uploads/40/16781/PEP308_RecommendedReleaseOptions.htm">

277 for more information.

PEP 308</a> for more information on these configuration options.

</li>

</ol>

<span

</blockquote>

style="font-family: monospace;">

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

<h2><a name="docs">Documentation</a></h2>

Much

<span

style="color: rgb(255, 0, 0); text-decoration: line-through;">Much

OpenPegasus

is documented in the <a

is documented in the <a href="http://www.openpegasus.org/pp/index.tpl?CALLER=index.tpl">Pegasus

href="http://www.openpegasus.org/pp/index.tpl?CALLER=index.tpl">Pegasus

Enhancement Process (PEPs)</a> which are the basis for approval

Enhancement Process (PEPs)</a> which are the basis for approval of

OpenPegasus functionality, changes, plans, etc.  The approved PEPs

OpenPegasus functionality, changes, plans, etc.  The approved

are publicly available on the OpenPegasus web site.<span

PEPs

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

are publicly available on the OpenPegasus web site.

Other

documentation available

Line 311

Line 362

source tree, see pegasus/doc/apidoc) and other miscellaneous

documentation

in the doc directory. Also, there is a set of Release Notes for each

release in the pegasus root

release in the OpenPegasus root

source directory of CVS.

Note that the <a

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

href="http://www.openpegasus.org/">OpenPegasus web

site</a> will be the source

of most

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

and

design documentation.

<h2><a name="part">How to Participate</a></h2>

<font

Contributors

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

are welcome to participate in the OpenPegasus development effort. Join

the mailing list by going to the <a

the mailing list by going to the <a href="http://www.openpegasus.org/mailinglists.tpl?CALLER=index.tpl">Mailing

href="http://www.openpegasus.org/mailinglists.tpl?CALLER=index.tpl">Mailing

Lists</a> web page from the OpenPegasus site.

<h1>

<a name="inst_peg">Installing OpenPegasus</a> </h1>

Line 333

Line 381

Refer to the <a href="#avail_of_peg">Availability</a>

section for instructions on obtaining source code.

If you want to install pre-built Pegasus

If you want to install

executables instead of building from source code, then refer to the <a

pre-built Pegasus

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

executables instead of building from source code, then refer to the <a href="http://www.openpegasus.org/pr/">RPM installation

instructions</a>.

<h2><a name="vfy_req_sw"></a>Verify Dependencies<span

style="font-weight: normal;"></h2>

<h2><a name="vfy_req_sw"></a>Verify

<span

Dependencies</h2>

style="font-weight: normal;">Before

Before

you build, install, or run OpenPegasus, be sure you have the proper set

of software

it depends on.  Refer to the section <a href="#peg_dep">Dependencies</a>

Line 348

Line 396

the complete list.

<h2><a name="set_envt_var">Set the Environment

<h2><a name="set_envt_var">Set the

Environment

Variables</a></h2>

Before building, installing, or running

Before building, installing,

or running

OpenPegasus, some environment variables may

have to be defined or updated.  See PEP 277 for the full list of

have to be defined or updated.  See PEP 292 for the full list

environment variables and configuration options for OpenPegasus. The

minimum set is:

<ul>

<li>PEGASUS_ROOT -- The directory

containing the pegasus root directory from CVS.</li>

containing the OpenPegasus root directory from CVS.</li>

<li>PEGASUS_HOME -- The directory

that will contain all output from building and running OpenPegasus, it

can be the same as PEGASUS_ROOT if desired.</li>

Line 371

Line 422

<h2><a name="bld_peg"></a>Build the Executables

</h2>

<div style="margin-left: 40px;">OpenPegasus

is compiled and linked using a make structure that recurses through the

is compiled and linked using a make structure that recurses through

source tree.

the  OpenPegasus source tree.

<span

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

Makefile commands

<div style="margin-left: 40px;"><span

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

Open<span

OpenPegasus

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

includes several Makefiles that enable

you to quickly build or

refresh files for the server, clients, providers, test cases, and

Line 405

Line 452

repository entries and other resources required by the tests, and then

executes all automated tests.</li>

</ul>

<span

For a comprehensive

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

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

list of  the

make targets, refer to pegasus/Makefile

make targets, refer to <big>pegasus/Makefile</big>

at the top of the OpenPegasus source directory.<span

at the top of the OpenPegasus source directory.

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

style="text-decoration: line-through; color: rgb(204, 51, 204);"><span

style="font-weight: bold;">

</div>

<ul>

</ul>

<h2><a name="pop_peg_rep">Populate the Repository</a> </h2>

<h2><a name="pop_peg_rep">Populate the Repository</a>

</h2>

Before using OpenPegasus you must populate the repository. Typically,

this

is done during the build process by the 'make repository' target<span

is done during the build process by the 'make repository' target.

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

However,

style="text-decoration: line-through;">. However,

you

can also compile MOF (Managed Object Format) code manually with the

cimmof compiler.

The 'make repository' target in pegasus<span

The 'make repository' target

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

in the makefile <big>pegasus/Makefile</big>

style="text-decoration: line-through;">/Makefile doe<span

performs several functions including:

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

style="text-decoration: line-through;">s several things:

<ul>

<li>Removes

<li>Removes the existing

the existing

repository (if one exists).

</li>

<li>Generates the default

CIM Schema (currently v2.9)

CIM Schema (defined in pegasus/mak/config.mak)

in the repository (skeleton of CIM

objects).  Refer to

objects).  Refer to PEGASUS_CIM_SCHEMA environment

PEGASUS_CIM_SCHEMA in PEP 277 for alternate versions.

variable  in  Pegasus PEP 308  to

set  alternate schema versions.

</li>

<li>Loads

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

Line 455

Line 496

src/Providers)

</li>

</ul>

<h2><a name="reg_prov">Register

Providers</a></h2>

OpenPegasus registers Providers using a

OpenPegasus registers

Providers using a

set of provider registration classes

encoded in MOF. This set of classes is close

to, but not

Line 473

Line 514

capabilities, 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 src/Providers/sample/Load directory for examples of

MOFs.  See the <big>pegasus/src/Providers/sample/Load</big>

directory for examples of

several registration instance implementations that do work with

OpenPegasus

today.

Line 482

Line 524

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

environment

variables set (eg. PEGASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM). 

variables set (eg. PEGASUS_HOME, PEGASUS_ROOT,

PEGASUS_PLATFORM). 

For

32 bit linux, the definition of PEGASUS_PLATFORM is normally

32 bit Linux, the definition of PEGASUS_PLATFORM is normally

LINUX_IX86_GNU. Use the g++

LINUX_IX86_GNU.   For 64 bit IX86  Linux the

compiler to compile and link the executables.

definition

PEGASUS_PLATFORM is normally LINUX_IX86_64_GNU.  Use the g++

compiler to compile and link the executables. All of the supported

platform

definitions are defined in <big>pegasus/mak</big>

as  make files with the

definition:

platform_<operatingSystem>_<architecture>_<compiler>

The

component is what forms the PEGASUS_PLATFORM environment variable so

that the

appropriate platform make file can be found during the build process.

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

about Building on Windows </a></h2>

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

Use of Windows 2000 SP3 or later is recommended.  OpenPegasus

regularly tested on both Windows 2000 and Windows XP using the

Microsoft Visual C++ compilers.

Today we build OpenPegasus on Windows

Today we build OpenPegasus

on Windows

using a set of Makefiles

contained

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

not supported, Visual Studio 6.0 (SP5) or later is supported) and the

GNUMAKE

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

make utility.  Note that you MUST have the OpenPegasus <a href="#mu_utility">mu.exe </a>utility compiled and

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

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

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

For Windows, try the

following for an

example environment:

<pre style="margin-left: 40px;">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 to 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

<pre style="margin-left: 40px;">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 to compile in debug mode set PEGASUS_DEBUG=true REM set PEGASUS_ROOT to top of source tree set PEGASUS_ROOT=C:/cimom/pegasus REM (Note: The '/' characters are intentional and required by the OpenPegasus build system). REM Also the disk designator (C:) is required for at least some newer versions of the Microsoft REM  compilers to avoid confusion between options and paths REM set PEGASUS_HOME to where you want repository and executables, it can be the same as PEGASUS_ROOT set PEGASUS_HOME=%PEGASUS_ROOT% REM set PEGASUS_PLATFORM for Windows set PEGASUS_PLATFORM=WIN32_IX86_MSVC REM setup the path to the runtime files. set path=%path%;%PEGASUS_HOME%\bin </pre>

class="norm">The '/' characters are intentional and required by the OpenPegasus build system) REM set PEGASUS_HOME to where you want repository and executables, it can be the same as PEGASUS_ROOT set PEGASUS_HOME=%PEGASUS_ROOT% REM set PEGASUS_PLATFORM for Windows<br

style="color: rgb(255, 0, 0);">set PEGASUS_PLATFORM=WIN32_IX86_MSVC 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>

Line 531

Line 590

commands. For example:

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

C:\>

mu rm myfile.cpp yourfile.cpp

You may type "mu" to get a list of valid

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

The MU utility supports

globing

(expansion of wildcards) so

you can do things like this:

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

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

MU is required to build

MU is required to build under the Windows

under the Windows

environment. MU is

available as part

of the distribution of OpenPegasus.

<div style="margin-left: 40px;">NOTE: The binary for MU.EXE is not

<div style="margin-left: 40px;">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

Line 560

Line 622

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

available as a zip file on the OpenPegasus <a href="http://www.openpegasus.org/pb/index.tpl?CALLER=index.tpl">Tools</a>

href="http://www.openpegasus.org/pb/index.tpl?CALLER=index.tpl">Tools</a>

web page.

</div>

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

Line 574

Line 635

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 (refer to PEP 277

installation is (refer to PEP 292

for more details on build variables).

You

must also have the PEGASUS_HAS_SSL variable defined. Then when you

must also have the PEGASUS_HAS_SSL environment variable defined. Then

when you

build

OpenPegasus, it

will include the SSL support.

<div style="margin-left: 40px;">Refer to the OpenPegasus SSL Guide

<div style="margin-left: 40px;">Refer to the OpenPegasus

SSL Guide

(found in doc/PegasusSSLGuidelines.htm)

for details on

using OpenPegasus with SSL,

Line 596

Line 659

CVS

environment, including:

<ul>

<li>Test Clients - There are several

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

clients that have been

built specifically to test OpenPegasus, or parts of OpenPegasus,

including

TestClient, Client, cimcli, ipinfo,

Line 610

Line 674

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

"make testrepository" target including: test namespaces, extra

classes and instances in those namespaces, and additional sample and

test providers.<span

test providers.</li>

style="color: rgb(255, 0, 0); text-decoration: line-through;"> </li>

</ul>

<li>Sample and Test Providers -  Test providers exist

</div>

<ul>

<li>Sample and Test Providers -

Test providers exist

for

the major provider types in the src/Providers/sample

and src/Providers/TestProviders directories. </li>

<li>Unit Tests - Most OpenPegasus functions include unit

</ul>

</div>

<ul>

</ul>

<ul>

<li>Unit Tests - Most OpenPegasus

functions include unit

tests

for

the functions.  These are normally executed with the "make

Line 631

Line 708

directory). Unit tests are executed with the CIM Server shutdown and

normally do not require the existence of class definitions in the

repository. </li>

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

</ul>

</div>

<li>End-to-end Test Suite - the directory

"test" contains

set of operatio<span

set of operation

style="color: rgb(255, 0, 0); text-decoration: line-through;">n

tests that cover the major CIM Operations.  See

tests that cover the major CIM Operations.  See<span

style="color: rgb(255, 0, 0); text-decoration: line-through;">

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>

Once OpenPegasus is

successfully built, the  tests can be executed through the

root Makefile

with targets such as:

<ul>

</ul>

<ul>

<li>make unittests - Execute the unit

tests. These do not depend on having a running server or repository

installed.  They test components of the OpenPegasus code.

These tests run to completion if successful but normally stop on the

first error found by a test program.</li>

<ul>

</ul>

</blockquote>

<ul>

<li>make servertests - Executes the

OpenPegasus end-to-end test suite against a running OpenPegasus server

starting and stopping the server as required to modify configuration

parameters. The repository must be installed for these tests to execute

and they are tested against the default repository as part of regular

OpenPegasus development and release testing. These tests will run to

successful completion if there are not errors detected but will

normally stop on the first error.  There is a subset of these

tests that can be run in an environment that does not have root

privileges but root privileges are required to run the complete suite.</li>

</ul>

</blockquote>

<ul>

</ul>

<li>make alltests - execute both the

unit and end-to-end tests.</li>

</ul>

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

ICU (International Components for

ICU (International

Components for

Unicode) refers to the set of

libraries that OpenPegasus uses to run with globalization support. For

example, these

Line 658

Line 777

pegasus/docs

directory for details.

When users run "make servertests"

When users run "make

servertests"

to verify the integrity of an OpenPegasus download, a series of tests

are

run that

Line 703

Line 823

for PEGASUS_MSG_HOME.

<hr>

Licensed to The Open Group (TOG) under one or more contributor

license

EMC Corporation; Symantec Corporation; The Open Group.

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

this work for additional information regarding copyright ownership.

Permission is hereby granted, free of charge, to any person obtaining a

Each contributor licenses this file to you under the OpenPegasus Open

copy

Source License; you may not use this file except in compliance with the

of this software and associated documentation files (the "Software"), to

License.

deal in the Software without restriction, including without limitation

Permission is hereby granted, free of charge, to any person

the

obtaining a

rights to use, copy, modify, merge, publish, distribute, sublicense,

copy of this software and associated documentation files (the

and/or

"Software"),

sell copies of the Software, and to permit persons to whom the Software

to deal in the Software without restriction, including without

is

limitation

furnished to do so, subject to the following conditions:

the rights to use, copy, modify, merge, publish, distribute,

sublicense,

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED

and/or sell copies of the Software, and to permit persons to whom the

IN

Software is furnished to do so, subject to the following conditions:

ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS

The above copyright notice and this permission notice shall be

PROVIDED

included

"AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING

in all copies or substantial portions of the Software.

BUT NOT

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

LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

KIND, EXPRESS

PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT

OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

AN

IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY

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

CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,

CONNECTION

TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE

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

SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

<hr>

</body>

</body></html>

</html>

Legend:

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

No CVS admin address has been configured