(file) Return to BuildAndReleaseOptions.html CVS log (file) (dir) Up to [Pegasus] / pegasus / doc

File: [Pegasus] / pegasus / doc / BuildAndReleaseOptions.html (download) / (as text)
Revision: 1.48, Mon Sep 15 06:52:13 2014 UTC (9 years, 6 months ago) by jsafrane
Branch: MAIN
Changes since 1.47: +37 -0 lines
BUG#: 9883
TITLE: Implement HTTP Negotiate authentication

DESCRIPTION: Implemented HTTP Negotiate authentication, as described in
RFC 4559. It uses SPNEGO protocol, GSSAPI as authentication API and MIT
Kerberos as GSSAPI implementation. The implementation should be
interchangeable, any GSSAPI implementation should work.

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

  <link rel="stylesheet" href="http://www.opengroup.org/stylesheets/info1.css"></head><body>
<hr>

<p align="center">
  <b><font size="4">Recommended OpenPegasus Build and Configuration Options for Selected Platforms</font></b>
</p>

<hr>

<p><b>Abstract: </b>
  This document defines a set of recommended options for building,
  testing and running OpenPegasus on a selected set of
  platforms. In this version of the document, platform-specific configuration
  information have been documented for the platforms described in the
  "Documented Platforms" section of this document.
</p>

<p><b>Note 1: </b>
  The recommendations defined in this document are not intended to document
  the feature set included in any vendor's OpenPegasus-based product.
  Rather, the purpose of this document is to provide input to vendors when
  making product decisions.<br>
</p>

<hr>

<h2>Definition of the Problem</h2>

<p>OpenPegasus supports a large number of build and runtime options.
Determining which options to use can be challenging. The purpose of this
document is to simplify the build, testing and administration of OpenPegasus
by providing a recommended, tested set of options.</p>

<h2>Documented Platforms</h2>

<p>Support for the OpenPegasus build and runtime options described in
this document varies by platform.&nbsp;&nbsp; In this version of the
document, platform-specific configuration information has been included
for the platforms described in the following table.&nbsp; For all other
platforms, please consult the OpenPegasus Platform Advocate for
additional information.</p>

<ul>
  <table bordercolordark="#666666" bordercolorlight="#CCCCCC" border="1" cellspacing="1" width="20%">
    <tbody><tr>
      <th align="center" bgcolor="#cae6ca">Platform</th>
      <th align="center" bgcolor="#cae6ca">Status</th>
    </tr>
    <tr align="left">
      <td>HPUX_IA64_ACC</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>HPUX_PARISC_ACC</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_IA64_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_IX86_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_PPC64_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_PPC_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_PPC_E500_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_SH4_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_XSCALE_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_ZSERIES64_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>LINUX_ZSERIES_GNU</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>VMS_ALPHA_DECCXX</td>
      <td>&nbsp;</td>
    </tr>
    <tr align="left">
      <td>VMS_IA64_DECCXX</td>
      <td>&nbsp;</td>
    </tr>
    </tbody></table>
</ul>

<h2>Proposed Solution</h2>

<h3>Security Considerations</h3>
<ol>
  <li>
    To avoid introducing security vulnerabilities, vendors must never
    ship providers incompatible with the security assumptions used in
    their deployment.
    For example, providers designed for a single-user deployment that
    don't perform authorization  must not be shipped with a CIM Server
    that expects the providers to perform authorization. Note that
    this authorization burden is considerably lighter if the provider
    is registered as 'run as requestor' and if the CIM Server enables
    that feature. See <a href="http://www.openpegasus.org/pp/uploads/40/7197/SecurityGuidePEP.htm">
    PEP#223 - Security Coding Guidelines</a> for additional
    details.
  </li>
  <li>
    Vendors should ensure they configure the CIM Server consistently
    with the security requirements of their deployment.
  </li>
</ol>

<h3>Terminology Notes</h3>
<ol>
  <li>
    In this document, the term "Not Set" is used to indicate
    that the a value for the environment variable has not been defined.
    "Set" is used to indicate that the value must be defined,
    but the actual value of the variable is not checked.
  </li>
</ol>

<h3>General Notes</h3>

<ol>
  <li>
    Not all functionality described in this document has achieved
    "Green"status, please refer to the
    <a href="http://www.openpegasus.org/page.tpl?CALLER=index.tpl&amp;ggid=799">
    OpenPegasus Project Feature Status </a>page for information on
    the maturity level of OpenPegasus features.
  </li>
  <li>
    To encourage testing of new functionality, recommendations for the
    Development Build may include features that are not yet recommended
    for Release Builds.
  </li>
</ol>

<h3>Environment Variable Settings for <u>Building</u> OpenPegasus</h3>

<h4>Definitions</h4>

<h5>ICU_INSTALL</h5>
<ul>
  <b>Description:&nbsp;</b>When set, points to the directory containing
     the <a href="%20http:/oss.software.ibm.com/icu"> ICU(International
     Components for Unicode)</a> installation. The 'include'
     subdirectory is used to locate ICU header files at build time. The
     'lib' subdirectory is used to locate ICU libraries at link
     time.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No.&nbsp; However, if PEGASUS_HAS_ICU is
     set and ICU_INSTALL is not defined, the ICU libraries and header
     files are expected to be installed in directories (e.g.,/usr/lib,
     /usr/include)&nbsp; that are searched by default.<br>
  <b>Considerations:&nbsp;</b>This environment variable is only used
     if PEGASUS_HAS_MESSAGES is set. Refer to PEGASUS_HAS_MESSAGES for
     additional details.
</ul>

<h5>ICU_ROOT_BUNDLE_LANG</h5>
<ul>
  <b>Description:&nbsp;</b>If set, specifies the language
     to be used to generate the root resource bundle.  The
     default value for ICU_ROOT_BUNDLE_LANG is _en.<br>
  <b>Default Value:&nbsp;</b>_en<br>
  <b>Recommended Value (Development Build):&nbsp;</b>No
     Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>No Recommendation<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This environment variable is
     only used if PEGASUS_HAS_MESSAGES is set. Refer to
     PEGASUS_HAS_MESSAGES for additional details.<br>
     If set, resource bundles for the designated language must
     exist for the following files:
     <ul>
       <li>pegasus/src/Pegasus/msg/Server/pegasusServer_en.txt</li>
       <li>pegasus/src/Pegasus/msg/Listener/pegasusListener_en.txt</li>
     </ul>
</ul>


<h5>OPENSSL_BIN</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the
     OpenSSL <i>binary</i> directory. <br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>No. By default, the openssl binary is
     expected to be installed in a directory that is searched by default
     (e.g., /usr/bin). For platforms where this isn't true, the
     OPENSSL_BIN environment variable may be used to define an
     alternative path. This environment variable is only used if
     PEGASUS_HAS_SSL is set.
</ul>

<h5>OPENSSL_HOME</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the OpenSSL
     SDK directory.  This directory must contain the OpenSSL
     <i>include</i> directory, $(OPENSSL_HOME)/include, and the OpenSSL
     <i>library</i> directory, $(OPENSSL_HOME)/lib.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>Yes for Windows, if PEGASUS_HAS_SSL
     is set. No for all other platforms. For AIX, the default
     value for OPENSSL_HOME is /usr/linux.&nbsp; For all other
     platforms, the OpenSSL include files and libraries are expected
     to be installed in directories that are searched by default (e.g.,
     /usr/bin, /usr/lib(64), and /usr/include).
     For platforms where the default value is not correct, the
     OPENSSL_HOME environment variable may be used to define an
     alternative path (i.e., $(OPENSSL_HOME)/lib and
     $(OPENSSL_HOME)/include). This environment variable
     is only used if PEGASUS_HAS_SSL is set.
</ul>

<h5>PEGASUS_ALLOW_ABSOLUTEPATH_IN_PROVIDERMODULE</h5>
<ul>
  <b>Description:&nbsp;</b>If set to true, a version of OpenPegasus
     will be built that allows an absolute path to be specified as the
     value of the Location property of PG_ProviderModule class.&nbsp;
     Otherwise it does not allow the absolute path to be specified.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<p>
  <b>Considerations:&nbsp;</b>To avoid introducing security
     vulnerabilities, vendors should analyze their deployment
     environments to understand the security implications of allowing
     providers to be loaded from a dynamically changing set of
     directories.<br>
</p></ul>

<h5>PEGASUS_CCOVER</h5>
<ul>
  <b>Description:&nbsp;</b>This flag is currently only supported on
     HP-UX. It is enabled on the Nightly Build &amp; Test system,
     HP-UX_11iv3_Integrity_C-Cover.&nbsp; This system is
     used to generate the nightly BullseyeCoverage code coverage
     metrics.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations: </b>This flag is only supported on HP-UX to enable
     CCOVER for the NB&amp;T system.<br>
</ul>

<h5>PEGASUS_CIM_SCHEMA</h5>
<ul>

  <b>Description:&nbsp;</b>This variable is used internally by the
OpenPegasus development team when testing OpenPegasus in the integrated
build/test environment. It defines the version of the CIM Schema (which
must exist in the $(PEGASUS_ROOT)/Schemas directory) that will be used
to build the class repository for testing the pegasus environment
("make repository", etc.).<br>
  <b>Default Value:&nbsp;</b>CIM241 (Note that this may change as newer versions of the CIM Schema are used as the default.<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>No <br>
  <b>Considerations:</b>
Additional code changes may be required when upgrading or downgrading
the CIM Schema version from the default.&nbsp; The default CIM Schema
is defined in the file $(PEGASUS_ROOT)/mak/config.mak.<br>
  <br>
<p></p>
</ul>


<h5>PEGASUS_CLASS_CACHE_SIZE</h5>
<ul>
  <b>Description:&nbsp;</b>This environment variable gives the size of
     the class cache used by CIM repository. This variable defines the
     size of the class cache (i.e., the maximum number of classes that
     may be included). If this variable is set to 0, class caching is
     disabled.<br>
  <b>Default Value:&nbsp;</b>8<br>
  <b>Recommended Value (Development Build):&nbsp;</b>8<br>
  <b>Recommended Value (Release Build):&nbsp;</b>8<br>
  <b>Required:&nbsp;</b>No <p></p>
</ul>

<h5>PEGASUS_DEBUG</h5>
<ul>
  <b>Description:&nbsp;</b>Builds a debug version of OpenPegasus.
     Concurrently, this flag controls a) enabling compiler specific
     debug flags and b) the inclusion of debug-specific
     functionality.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No
</ul>

<h5>PEGASUS_DEFAULT_USERCTXT_REQUESTOR</h5>
<ul>
  <b>Description:&nbsp;</b> If set to true, the <i>Requestor</i> user
     context is used for providers that do not specify a UserContext
     value in their registration. Otherwise, the <i>Privileged</i> user
     context value is used by default. <br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Value (Development Build):&nbsp;</b>false<br>
  <b>Recommended Value (Release Build):&nbsp;</b>false<br>
  <b>Required:&nbsp;</b>No
  <b>Considerations:</b> Use of the <i>Requestor</i> default has
     improved provider security characteristics. However, some providers
     may not operate correctly when run in the <i>Requestor</i> user
     context and setting this value to true may cause those providers to
     fail.&nbsp; Providers that can run in the <i>Requestor</i>
     user context are encouraged to explicitly set the UserContext value
     in their registration rather than rely on the default setting
     default by this variable. Please refer to
     SecurityGuidelinesForDevelopers.html. PEP 223 for a discussion
     of the rationale/advantages of running providers in the
     <i>Requestor </i> user context. <b>Note:</b> This build
     variable is not meaningful if the Provider User Context feature is
     disabled with the PEGASUS_DISABLE_PROV_USERCTXT
     setting.&nbsp;
</ul>


<h5>PEGASUS_DEFAULT_ENABLE_OOP</h5>
<ul>
  <b>Description:&nbsp;</b>When this variable is set to false, by
     default, Providers are run in the cimserver process
     (forceProviderProcesses=false). If this value is set true,
     Providers are run out-of-process by default.<br>
  <b>Default Value:&nbsp;</b>true for HP-UX and Linux, false for
     other platforms<br>
  <b>Recommended Value (Development Build):&nbsp;</b>true (HP-UX,
     Linux)<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true (HP-UX,
     Linux)<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations: </b>This environment variable can be used to
     change the "hard-coded" default setting for the
     forceProviderProcesses configuration value.&nbsp;
     Refer to the definition of <b>forceProviderProcesses</b> for
     additional information.
</ul>

<h5>PEGASUS_DEST_LIB_DIR</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of OpenPegasus
     shared libraries.<br>
  <b>Default Value:&nbsp;</b>$(PEGASUS_HOME)/lib<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     $(PEGASUS_HOME)/lib<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation <br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This variable is NOT is used to define
     the location of the Provider library directories.&nbsp;
     Please refer to the providerDir configuration option for details
     on defining the directories for the Provider libraries.
</ul>


<h5>PEGASUS_DISABLE_DEPRECATED_INTERFACES</h5>
<ul>
  <b>Description:&nbsp;</b>Removes deprecated symbol definitions
     from OpenPegasus runtime libraries.<br>
  <b>Default Value:</b>&nbsp;Not Set<br>
  <b>Recommended Value (Development Build):</b>&nbsp;Not Set<br>
  <b>Recommended Value (Release Build): </b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>If this option is set, the resulting
     OpenPegasus libraries will not be binary compatible with
     clients and providers built using interface definitions from
     prior releases. This option may be used to slightly reduce binary
     footprint in an environment where compatibility is not required.<br>
</ul>

<h5>PEGASUS_DISABLE_INSTANCE_QUALIFIERS</h5>
<ul>
  <b>Description:&nbsp;</b>In the CIM Infrastructure Specification,
     version 2.3, the DMTF clarified that instance-level qualifiers are
     not allowed.&nbsp; In Version 1.2 of the Specification CIM
     Operations over HTTP, use of the IncludeQualifiers parameter has
     been DEPRECATED.<br>
  <b>Default Value:</b>&nbsp;Not Set<br>
  <b>Recommended Value (Development Build):</b>&nbsp;Not Set<br>
  <b>Recommended Value (Release Build): </b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Existing CIM Clients may depend on
     qualifiers being returned in the response. In this case, the
     PEGASUS_DISABLE_INSTANCE_QUALIFIERS should not be set.&nbsp;
     If this flag is set, the value of the IncludeQualifiers parameter
     passed on the GetInstance and EnumerateInstance operations is
     ignored and qualifiers are not returned.&nbsp;
     Disabling the return of qualifiers as part of a CIM Instance will
     improve performance.<br>
</ul>

<h5>PEGASUS_DISABLE_LOCAL_DOMAIN_SOCKET</h5>
<ul>
  <b>Description:&nbsp;</b>Disables support for local (same-system)
     connections over a Unix domain socket. If this option is NOT set,
     the CIM Server is built to allow connections to be established
     using a domain socket rather than a TCP port.<br>
  <b>Default Value:&nbsp;</b>Not Set&nbsp; <br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>(1) In high-threat environments, a
     customer may want to disable all ports or reduce the number of
     exposed network ports. Supporting a local connection mechanism
     using Unix domain socket allows the CIM Server to continue to
     receive and process requests from local CIM Clients. (2)
     Enabling this option may result in lose of functionality when
     sslClientVerificationMode = required. (3)The
     "LOCAL_DOMAIN_SOCKET" functionality has not been
     implemented for&nbsp; Windows or OpenVMS.&nbsp; Therefore, by
     default, this option is "Set" for Windows and OpenVMS
     platforms.
</ul>

<h5>PEGASUS_DISABLE_PERFINST</h5>
<ul>
  <b>Description:&nbsp;</b>Builds a version of OpenPegasus that
     disables support for gathering performance data.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build): </b>Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>The CIM_ObjectManager.GatherStatisticalData
     property is used to control statistic gathering.&nbsp; Once enabled,
     statistical data can be viewed by retrieving instances of the
     CIM_StatisticalData class. Support for gathering performance
     data requires PEGASUS_ENABLE_INTEROP_PROVIDER to be enabled. If
     PEGASUS_ENABLE_INTEROP_PROVIDER is explicitly disabled (i.e., set
     to false),&nbsp; then PEGASUS_DISABLE_PERFINST must be set to
     true.&nbsp; If PEGASUS_DISABLE_PERFINST is not defined or set to
     false and PEGASUS_ENABLE_INTEROP_PROVIDER is not set,
     PEGASUS_ENABLE_INTEROP_PROVIDER will be automatically enabled.
</ul>

<h5>PEGASUS_DISABLE_PRIVILEGED_TESTS</h5>
<ul>
  <b>Description:&nbsp;</b>This variable is used only in the development
     environment to restrict the level of testing performed by default.
     If set, tests that require the CIM Server to run in a privileged
     mode will not be run.&nbsp; Setting this variable allows
     developers, without privileged access, to successfully run a
     subset of the OpenPegasus test suit.&nbsp; This variable does
     not affect CIM Server functionality.&nbsp; It merely controls
     the level of testing.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Used<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Enabling this variable will significantly
     reduce the testing of security related features (e.g.,
     authentication and authorization) and can affect testing in other
     areas.
</ul>

<h5>PEGASUS_DISABLE_PROV_USERCTXT</h5>
<ul>
  <b>Description:&nbsp;</b>Builds a version of OpenPegasus that
     disables supports for the Provider User Context feature.&nbsp;
     This feature allows a Provider to choose the user context in
     which it is invoked, including the ability to run in the context of
     the user requesting an operation.<br>
  <b>Default Value:&nbsp;</b>Set for Windows and OpenVMS, Not Set
     for all other platforms<br>
  <b>Recommended Value (Development Build): </b>Set for Windows and
     OpenVMS, Not Set for all other platforms<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Set for Windows and
     OpenVMS, Not Set for all other platforms<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>The Provider User Context feature may be
     disabled by compiling with the PEGASUS_DISABLE_PROV_USERCTXT flag
     defined. In this case, the Provider Registration Manager rejects
     provider registration requests that specify a UserContext property
     value. The user context in which providers run is then unchanged by
     this enhancement. Some platforms, such as OS/400 and z/OS may
     define the PEGASUS_DISABLE_PROV_USERCTXT as part of the platform
     configuration, since these platforms already set the provider user
     context on a per-thread basis.&nbsp; When the Provider User Context
     feature is enabled, support for each of the User Context types may
     be disabled individually. Provider registration fails when an
     unsupported UserContext value is specified. Please refer to
     SecurityGuidelinesForDevelopers.html / PEP 223 for a discussion of
     the rationale/advantages of user context providers to many
     platforms.<br>
</ul>

<h5>PEGASUS_EXTRA_PROVIDER_LIB_DIR</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the extra provider
     libraries which are part of the release builds.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b> No.<br>
  <b>Considerations:&nbsp;</b> Since providerDir config property is fixed
     and hidden in release builds, this build time option provides facilty
     to include the extra provider directories without any security problems.
     This build time option is useful only when PEGASUS_OVERRIDE_DEFAULT_RELEASE_DIRS
     is set.
</ul>

<h5>PEGASUS_EMANATE_INCLUDE_DIR</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the EMANATE
     <i>include</i> directory. <br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>No. By default, the EMANATE include files
     are expected to be installed in directories that are searched by
     default (e.g., /usr/include). For platforms where this isn't true,
     the PEGASUS_EMANATE_INCLUDE_DIR environment variable may be used to
     define an alternative path. This environment variable is only used
     if PEGASUS_USE_EMANATE is set.<br>
  <b>Considerations: </b>Refer to the description of PEGASUS_USE_EMANATE
     for additional details.<br>
</ul>

<h5>PEGASUS_EMANATE_LIB_DIR</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the EMANATE
     <i>lib</i> directory. <br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>No. By default, the EMANATE libraries are
     expected to be installed in directories that are searched by
     default (e.g., /usr/lib, /usr/lib64). For platforms where this
     isn't true, the PEGASUS_EMANATE_LIB_DIR environment variable may
     be used to define an alternative path. This environment variable
     is only used if PEGASUS_USE_EMANATE is set.<br>
  <b>Considerations: </b>Refer to the description of PEGASUS_USE_EMANATE
     for additional details.<br>
</ul>

<h5>PEGASUS_ENABLE_AUDIT_LOGGER</h5>
<ul>
  <b>Description:&nbsp;</b>When this variable is set to false, support
     for audit logging will NOT be built into OpenPegasus. If this
     variable is set to true, or not set, support for audit logging
     will be included in the build. All other values are invalid.<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true<br>
  <b>Required:&nbsp;</b>No<br>
</ul>


<h5>PEGASUS_ENABLE_CMPI_PROVIDER_MANAGER</h5>
<ul>
  <b>Description:&nbsp;</b>If set to true, a version of OpenPegasus
     that supports CMPI providers and their dependent components is
     built.&nbsp; If this variable is not set or set to false, support
     for CMPI providers will not be included. <br>
  <b>Default Value:&nbsp;</b>true for Linux and OpenVMS, false for
     other platforms<br>
  <b>Recommended Value (Development Build): </b>true (Linux
     Platform Only)<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true (Linux Platform
     Only)<br>
  <b>Required:&nbsp;</b>No<p></p>
</ul>

<h5>PEGASUS_ENABLE_COMPRESSED_REPOSITORY</h5>
<ul>
  <b>Description:&nbsp;</b>If set the Repository Compression logic is
     built and enabled and compressed and non compressed repositories
     are supported. If not set then compressed repositories are not
     supported.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<p>
  <b>Considerations:&nbsp;</b>See
     pegasus/readme.compressed_repository</p>
</ul>


<h5>PEGASUS_ENABLE_CQL</h5>
<ul>
  <b>Description:&nbsp;</b>When this variable is set to false, support
     for Indication Subscription filters that have CQL as the language
     is disabled. It does not remove CQL from the build.<br>
  <b>Default Value:</b>&nbsp;Not Set<br>
  <b>Recommended Value (Development Build):</b>&nbsp;Not Set<br>
  <b>Recommended Value (Release Build):</b>&nbsp;false<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>The DMTF CIM Query Language
     Specification is Preliminary and subject to backward incompatible
     changes.
</ul>

<h5>PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT</h5>
<ul>
  <b>Description: </b>When this variable is set to true, support the
     DMTF Indications Profile (DSP1054) is included in OpenPegasus.&nbsp;
     If this variable is not set or set to false, support for the DMTF
     Indications Profile will not be included.<br>
  <b>Default Value:</b>&nbsp;Not Set<br>
  <b>Recommended Value (Development Build):</b>&nbsp;Not Set<br>
  <b>Recommended Value (Release Build):</b>&nbsp;Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations: </b>The implementation of this feature is
     based on a preliminary version of the DMTF Indications Profile,
     DSP1053, and subject to change.&nbsp; If this variable is enabled,
     two DMTF experimental class definitions, CIM_IndicationService and
     CIM_IndicationServiceCapabilities, will be added to the
     root/PG_InterOp namespace. Experimental class definitions are
     subject to change.&nbsp;
     PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT requires
     PEGASUS_ENABLE_INTEROP_PROVIDER to be enabled.
     If PEGASUS_ENABLE_INTEROP_PROVIDER is not set, setting
     PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT to true, will also
     enable PEGASUS_ENABLE_INTEROP_PROVIDER.  If
     PEGASUS_ENABLE_INTEROP_PROVIDER is explicitly disabled (i.e., set
     to false), a build error will be generated.
</ul>

<h5>PEGASUS_ENABLE_EXECQUERY</h5>
<ul>
  <b>Description:&nbsp;</b>When this environment variable is set,
     processing of ExecQuery operations is enabled. When not set,
     ExecQuery operation requests get a NotSupported response. (Note:
     The PEGASUS_ENABLE_EXECQUERY environment variable controls
     the definition of the PEGASUS_DISABLE_EXECQUERY compile macro.) <br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No
</ul>

<h5>PEGASUS_ENABLE_EMAIL_HANDLER</h5>
<ul>
  <b>Description:&nbsp;</b> When this environment variable is set, an
     E-Mail Indication Handler is built as part of the OpenPegasus
     build.&nbsp; The E-Mail Indication Handler can be used to
     delivered CIM Indications to a designated e-mail address.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>If PEGASUS_ENABLE_EMAIL_HANDLER is
     not set when OpenPegasus is built, a request to create an Email
     Indication Handler instance will be rejected will the error
     CIM_ERR_NOT_SUPPORTED.
</ul>

<h5>PEGASUS_ENABLE_GCOV</h5>
<ul>
  <b>Description:&nbsp;</b>GCOV,
     <a href="http://gcc.gnu.org/onlinedocs/gcc/index.html#toc_Gcov">
     http://gcc.gnu.org/onlinedocs/gcc/index.html#toc_Gcov</a>, is a
     code coverage utility.&nbsp; If PEGASUS_ENABLE_GCOV is set,&nbsp;
     GCC will instrument the code to support analysis by GCOV.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br><b>Considerations:&nbsp;</b>
     This flag is currently only supported with GCC on Linux.
     <ul>
       Note: LCOV, <a href="http://ltp.sourceforge.net/coverage/lcov.php">
       http://ltp.sourceforge.net/coverage/lcov.php</a>, is a
       graphical front-end extension for GCOV. It collects GCOV data
       for multiple source files and creates HTML pages with coverage
       information. You can use the following steps to use LCOV to
       analyze OpenPegasus GCOV data.
       <ol>
         <li>Set PEGASUS_ENABLE_GCOV = true.</li>
         <li>Build and test OpenPegasus (e.g.,
             <i>make -f pegasus/TestMakefile&nbsp; build
             alltests</i>).</li>
         <li>For each source directory,
           <ul>
             <li>copy the .gcda and .gcno files from the object
                 directory to the source directory (e.g.,
                 <i>cp build/obj/Pegasus/Common/*.gcda
                 src/Pegasus/Common/</i>);</li>
             <li>execute the <b>lcov</b> command
                (e.g.,
                <i>lcov --directory src/Pegasus/Common/ --capture
                --output-file result.info</i>) to build the result.info
                file; and finally,</li>
             <li>use the <b>genhtml</b> command to generate the .html
                 output (e.g., <i>genhtml result.info</i>).&nbsp; The
                 top .html file is named index.html.</li>
	   </ul>
       </li></ol>
    </ul>
</ul>

<h5>PEGASUS_ENABLE_INDICATION_COUNT</h5>
<ul>
  <b>Description: </b>If true, the CIM
     Server will be built to count the number of CIM indications
     generated by providers and matched with subscriptions. If false
     or not set, indication statistic support will not be included.
  <b>Default Value: </b>true<br>
  <b>Recommended Value (Development Build): </b>true <br>
  <b>Recommended Value (Release Build): </b>true <br>
  <b>Required: </b>No <br>
  <b>Considerations: </b>The number of CIM indications generated by
     providers and matched with subscriptions is stored in hash tables
     which causes memory usage to increase by 4 bytes for each
     active subscription and by about 400 bytes for each active
     indication provider.<br>	
</ul>

<h5>PEGASUS_ENABLE_PROTOCOL_BINARY</h5>
<ul>
  <b>Description: </b>If true, OpenPegasus uses a faster binary
     protocol between local clients and the CIM server. If false, OpenPegasus 
     uses the conventional XML-based protocol instead.
     See PEP#340 for more details.
     <br>
  <b>Default Value: </b>false<br>
  <b>Recommended Value (Development Build): </b>false<br>
  <b>Recommended Value (Release Build): </b>false<br>
  <b>Required: </b>No<br>
  <b>Considerations: </b>This option improves performance by using a faster
     binary protocol between local clients and the CIM server.
     <br>
</ul>

<h5>PEGASUS_ENABLE_INTEROP_PROVIDER</h5>
<ul>
  <b>Description: </b>If true, the OpenPegasus Interop Provider
     will be build.  If false or not set, the OpenPegasus Interop
     Provider will not be built.<br>
  <b>Default Value: </b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build): </b>false<br>
  <b>Required: </b>No <br>
  <b>Considerations: </b>&nbsp;A number of features controlled by
     OpenPegasus build options are dependent on the Interop
     Provider.&nbsp; Please refer to PEGASUS_ENABLE_SLP,
     PEGASUS_DISABLE_PERFINST, and
     PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT for additional
     details.<br>
</ul>

<h5>PEGASUS_INTEROP_NAMESPACE</h5>
<ul>
  <b>Description: </b>This variable is used for configuring the Interop 
     namespace name. This option helps to establish a consistent Interop 
     Namespace as mentioned in DMTF specification.(DSP1033)<br>
  <b>Default Value: </b>root/PG_InterOp<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build): </b>Not Set<br>   
  <b>Required: </b>No <br>
  <b>Considerations:&nbsp;</b>The accepted values for this environment 
     variable are "root/PG_InterOp" or "interop" or "root/interop". For 
     any other value, the default value will be used.With the usage of 
     this build option, we have to start using pegasus with fresh repository.
</ul>

<h5>PEGASUS_ENABLE_IPV6</h5>
<ul>
  <b>Description:&nbsp;</b>This variable can be used to specify
     whether IPv6 support should be included in OpenPegasus.<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Value (Development Build): </b>true<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>When this variable is set to
     'false', support for IPv6 socket APIs and structures is disabled,
     and the CIM Server will not accept connections to or from IPv6
     network interfaces. When this variable is set to 'true', the
     newer IPv6 socket APIs and structures will be included when
     OpenPegasus is built, so they must be supported on the build
     platform. However, if IPv6 is not supported on the platform on
     which an IPv6-enabled version of OpenPegasus is run, then the IPv6
     feature will be disabled at run-time and only IPv4 connections
     will be supported.
</ul>

<h5>PEGASUS_ENABLE_JMPI_PROVIDER_MANAGER</h5>
<ul>
  <b>Description:&nbsp;</b>If true, a version of OpenPegasus that
     supports JMPI providers and their dependent components is built.
     If false or not set, support for JMPI Providers is not included
     in OpenPegasus.&nbsp; All other values are invalid.<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Value (Development Build):&nbsp;</b>false<br>
  <b>Recommended Value (Release Build):&nbsp;</b>false<br>
  <b>Required:&nbsp;</b>No<p></p>
</ul>

<h5>PEGASUS_ENABLE_OBJECT_NORMALIZATION</h5>
<ul>
  <b>Description:&nbsp;</b>If set, builds in support so that objects
     returned from provider instance operations can be validated.
     The enableNormalization must also be set to 'true' (default)<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No&nbsp;&nbsp;&nbsp; <br>
  <b>Considerations: </b>If PEGASUS_ENABLE_OBJECT_NORMALIZATION is
     set, two new configuration options are defined: enableNormalization
     and excludeModulesFromNormalization.
</ul>

<h5>PEGASUS_ENABLE_PRIVILEGE_SEPARATION</h5>
<ul>
  <b>Description:&nbsp;</b>If true, a version of OpenPegasus that
     enables the Privilege Separation feature is built. This feature
     allows the CIM Server to run in a non-privileged user context and
     use a small executor process to perform privileged operations. If
     false or not set, the Privilege Separate feature will not be
     included.<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Value (Development Build):&nbsp;</b>true (HP-UX,
     Linux)<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true (HP-UX,
     Linux)<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b> The Privilege Separation feature is
     only supported on HP-UX and Linux platforms. The 'cimsrvr' user
     must be defined on the system. If the umask setting in the
     environment is not 0, PEGASUS_TMP must be set to a directory that
     is writable by the 'cimsrvr' user for the tests to run
     successfully.
</ul>

<h5>PEGASUS_ENABLE_PROTOCOL_WSMAN</h5>
<ul>
  <b>Description:&nbsp;</b>If true, a version of OpenPegasus is
     built that accepts and processes WS-Management requests. This
     feature is initially limited to WS-Transfer and WS-Enumeration
     operations. If false or not set, WS-Management support is not
     built or included in any way.<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Value (Release Build):&nbsp;</b>false<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b> The WS-Management standards are not
     mature, and interoperability problems may arise. The WS-Management
     functionality may change in incompatible ways in subsequent
     releases. Also note the known limitations specified in PEP 311.<br>
</ul>

<h5>PEGASUS_ENABLE_PROTOCOL_WEB</h5>
<ul>
  <b>Description:&nbsp;</b>Enable pegasus to act as webserver capable
     of serving webpages by comsuming the JSON output from CIM-RS.<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b> When authentication is disabled, Anybody can
  modify the pegasus cimserver. Please enable authentication when using
  webadmin to prevent unauthorized access. <br>
</ul>


<h5>PEGASUS_ENABLE_REMOTE_CMPI</h5>
<ul>
  <b>Description:&nbsp;</b>If set, a version of OpenPegasus that
     support Remote CMPI providers and their dependent components
     is built.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<p></p>
</ul>

<h5>PEGASUS_ENABLE_SLP</h5>
<ul>
  <b>Description:&nbsp;</b>This variable controls of the inclusion
     of SLP functionality in the OpenPegasus build.&nbsp;When this
     environment variable is set to 'true', SLP functionality will be
     included as part of the OpenPegasus build.&nbsp; If
     this variable is set to 'false' or not set, the SLP functionality
     will not be included.&nbsp; All other values are considered
     invalid and will result in a build error
     (e.g., "PEGASUS_ENABLE_SLP ($(PEGASUS_ENABLE_SLP)) invalid,
     must be true or false").<br>
  <b>Default Value: </b>'true' for Windows; 'false' for all other
     Platforms<br>
  <b>Recommended Value (Development Build):&nbsp;</b>'true' for
     Windows; 'false' for all other Platforms<br>
  <b>Recommended Value (Release Build):&nbsp;</b><br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>PEGASUS_ENABLE_SLP requires
     PEGASUS_ENABLE_INTEROP_PROVIDER to be enabled. If
     PEGASUS_ENABLE_INTEROP_PROVIDER is not set, setting
     PEGASUS_ENABLE_SLP to true, will also enable
     PEGASUS_ENABLE_INTEROP_PROVIDER. If
     PEGASUS_ENABLE_INTEROP_PROVIDER is explicitly disabled
     (i.e., set to false), a build error will be generated.<br>
</ul>


<h5>PEGASUS_ENABLE_SORTED_DIFF</h5>
<ul>
  <b>Description:&nbsp;</b>This controls if the DIFFSORT function
     is used rather than a simple DIFF of the test results files
     to the static results file. Set to 'true' enables the sorted
     diffs of results to static results files. Otherwise results
     in regular diffs of results to static results files.
     See OpenPegasus bug 2283 for background information concerning
     this config variable. <br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true<br>
  <b>Required:&nbsp;</b>No<p>&nbsp;</p>
</ul>

<h5>PEGASUS_ENABLE_SYSTEM_LOG_HANDER</h5>
<ul>
  <b>Description:&nbsp;</b>When this environment variable is set, a
     SysLog Indication Handler is built as part of the OpenPegasus
     build.&nbsp; The SysLog Indication Handler can be used to
     delivered CIM Indications to the system log file.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>If PEGASUS_ENABLE_SYSTEM_LOG_HANDLER
     is not set when OpenPegasus is built, a request to create a SysLog
     Indication Handler instance will be rejected with the error
     CIM_ERR_NOT_SUPPORTED.<br>
</ul>

<h5>PEGASUS_ENABLE_USERGROUP_AUTHORIZATION</h5>
<ul>
  <b>Description:&nbsp;</b>Builds a  version of OpenPegasus that
     allows an administrator to restrict access to CIM operations
     to members of a designated set of groups.&nbsp; Refer to the
     <b>authorizedUserGroups</b>configuration option for additional
     details.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Set<br>
  <b>Required:&nbsp;</b>No<br>
</ul>

<h5>PEGASUS_EXTRA_C_FLAGS</h5>
<ul>
  <b>Description:&nbsp; </b>This environment variable allows a
     developer to specify an additional set of flags to be included
     on&nbsp; the C compile command line.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>No Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No
</ul>

<h5>PEGASUS_EXTRA_CXX_FLAGS</h5>
<ul>
  <b>Description:&nbsp; </b>This environment variable allows a
     developer to specify an additional set of flags to be included
     on the C++ compile command line.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No
</ul>

<h5>PEGASUS_EXTRA_LIBRARY_LINK_FLAGS</h5>
<ul>
  <b>Description:&nbsp; </b>This environment variable allows a
     developer to specify an additional set of flags to include on
     the link command line used to build a library.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No
</ul>

<h5>PEGASUS_EXTRA_LINK_FLAGS</h5>
<ul>
  <b>Description:&nbsp; </b>This environment variable allows a
     developer to specify an additional set of flags to be included
     on the link command line.&nbsp; These flags will be included on
     both library and program executable link command lines.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No
  <b>Considerations: </b>Refer to PEGASUS_EXTRA_LIBRARY_LINK_FLAGS and
     PEGASUS_EXTRA_PROGRAM_FLAGS to add flags specific to either a
     library or program link command line.<br>
</ul>

<h5>PEGASUS_EXTRA_PROGRAM_LINK_FLAGS</h5>
<ul>
  <b>Description:&nbsp; </b>This environment variable allows a
     developer to specify an additional set of flags to include on
     the link command line used to build an executable program.<br>
  <b>Recommended Value (Development Build): </b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No
</ul>

<h5>PEGASUS_HAS_MESSAGES</h5>
<ul>
  <b>Description:&nbsp;</b>When set (to anything) during the build,
     OpenPegasus compiles with localization support.  The
     ICU (International Components for Unicode) variables,
     ICU_ROOT and ICU_INSTALL, indicate that the
     localization support is based on ICU.  Only ICU is supported
     at this time.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>If the PEGASUS_HAS_MESSAGES is not
     set, OpenPegasus is built without localization support.  This
     means that all messages sent by the CIM Server and the CLIs are in
     English. ICU is an open source project at
     <a href="http://oss.software.ibm.com/icu">
     http://oss.software.ibm.com/icu</a>.
     Only English translations are included with the OpenPegasus
     distribution. The OpenPegasus distribution does not provide
     translated messages. But, enabling for ICU would allow vendor to
     provide the translations. Refer to the OpenPegasus Release README
     for additional information regarding the use of ICU. Although, in
     OpenPegasus 2.3.2, experience with localization support
     has been limited to a select set of platforms, wider platform
     adoption of this technology is planned for 2.5.<br>
</ul>

<h5>PEGASUS_HAS_SSL</h5>
<ul>
  <b>Description:&nbsp;</b>If set, a version of OpenPegasus that
     supports SSL (i.e., https) is built.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Support for SSL in OpenPegasus is
     dependent on the OpenSSL software developed by the
     <a href="http://www.openssl.org/">
     OpenSSL Project (http://www.openssl.org/)</a>.

     If the PEGASUS_HAS_SSL variable is set, the variable OPENSSL_HOME
     must also be defined. The OPENSSL_HOME variable is used, by the
     OpenPegasus build, to determine the location of the OpenSSL
     include files, libraries and binaries.
</ul>

<h5>PEGASUS_HOME</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the
     OpenPegasus working directory.  The OpenPegasus
     build will use this directory as the default location
     for files generated during the build (e.g., binaries,
     libraries, objects).<br>
  <b>Default Value:&nbsp;</b>None<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>The error "PEGASUS_HOME
     environment variable undefined" is returned if the
     PEGASUS_HOME environment variable is not set.
     This variable is also used during runtime. Refer to the section
     titled "Environment Variable Settings for Running OpenPegasus
     2.3.2 on Linux" for additional details.<br>
</ul>

<h5>PEGASUS_MAX_THREADS_PER_SVC_QUEUE</h5>
<ul>
  <b>Description:&nbsp;</b>Controls the maximum number of threads
     allowed per message service queue. It is allowed to range
     between 1 and MAX_THREADS_PER_SVC_QUEUE_LIMIT (currently 5000)
     as set in pegasus/src/Pegasus/Common/MessageQueueService.cpp.
     If set to 0 (zero) the max threads per service queue is then
     set to MAX_THREADS_PER_SVC_QUEUE_LIMIT. If set larger than the
     MAX_THREADS_PER_SVC_QUEUE_LIMIT it is set equal to
     MAX_THREADS_PER_SVC_QUEUE_LIMIT. There are no other limits on the
     total number of threads that can exist within the system at this
     time. When the server starts there on the order of 10 to 20
     message service queues created dependent upon
     build options.&nbsp; <br>
  <b>Default Value:&nbsp;</b>5<br>
  <b>Recommended Value (Development Build):&nbsp;</b>5<br>
  <b>Recommended Value (Release Build):&nbsp;</b>5<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations: </b>This flag affects consumption of
     system resources. Not setting, or inappropriately setting
     this value, may cause the cimserver to hang or crash.<br>
</ul>

<h5>PEGASUS_ROOT</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the directory
     that corresponds to "pegasus" source directory defined in the
     OpenPegasus CVS source tree.  This environment variable is
     used by the OpenPegasus build to locate the required build
     and source files (e.g., $(PEGASUS_ROOT)/mak and
     $(PEGASUS_ROOT)/src).<br>
  <b>Default Value:&nbsp;</b>None<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>The error "PEGASUS_ROOT environment
     variable undefined" is returned if the PEGASUS_ROOT
     environment variable is not set.
</ul>


<h5>PEGASUS_NET_SNMP_INCLUDE_DIR</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the NET-SNMP
     <i>include</i> directory. <br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>No. By default, the NET-SNMP include
     files are expected to be installed in directories that
     are searched by default (e.g., /usr/include). For platforms
     where this isn't true, the PEGASUS_NET_SNMP_INCLUDE_DIR
     environment variable may be used to define an alternative path.
     This environment variable is only used if PEGASUS_USE_NET_SNMP
     is set.<br>
</ul>

<h5>PEGASUS_NET_SNMP_LIB_DIR</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the NET-SNMP
     <i>lib </i>directory. <br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>No. By default, the NET-SNMP library is
     expected to be installed in a directory that is searched by
     default (e.g., /usr/lib, /usr/lib64). For platforms where
     this isn't true, the PEGASUS_NET_SNMP_LIB_DIR environment
     variable may be used to define an alternative path. This
     environment variable is only used if PEGASUS_USE_NET_SNMP is set.
</ul>


<h5>PEGASUS_NOASSERTS</h5>
<ul>
  <b>Description:&nbsp;</b>Defines the NDEBUG compilation macro, which
     causes the preprocessor to remove PEGASUS_ASSERT() and disables assertion
     on PEGASUS_FCT_EXECUTE_AND_ASSERT statements.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Set<br>
  <b>Required:&nbsp;</b>No<br>
</ul>

<h5>PEGASUS_OPENSLP_HOME</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the OpenSLP
     SDK directory.  This directory must contain the OpenSLP
     <i>include</i> directory, $(PEGASUS_OPENSLP_HOME)/include,
     and the OpenSLP <i>library</i> directory,
     $(PEGASUS_OPENSLP_HOME)/lib.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>No. If not set, no additional include or
     library search paths will be included.
  <b>Considerations: </b>This value is not used if PEGASUS_USE_OPENSLP
     is not defined. <br>
</ul>

<h5>PEGASUS_PAM_AUTHENTICATION</h5>
<ul>
  <b>Description:&nbsp;</b>Enables support for PAM-(Pluggable
     Authentication Modules) based authentication.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Support for PAM in OpenPegasus is
     dependent on platform support for PAM.<br>
</ul>

<h5>PEGASUS_PAM_SESSION_SECURITY</h5>
<ul>
  <b>Description:&nbsp;</b>Enables support for PAM-(Pluggable
     Authentication Modules) based authentication and authorization.<br>
     When choosing this PAM method the PAM session started through pam_start
     is kept open for the complete CIM request.
     The PAM item PAM_RHOST will be set to the connection IP address.
     This allows PAM modules to restrict number of concurrent connections
     from a single host.<br>
     If PEGASUS_PAM_SESSION_SECURITY is set, you cannot enable the Privilege
     Separation feature (PEGASUS_ENABLE_PRIVILEGE_SEPARATION) or the 
     authentication-only PAM mechanism (PEGASUS_PAM_AUTHENTICATION).<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Support for PAM in OpenPegasus is
     dependent on platform support for PAM.<br>
</ul>

<h5>PEGASUS_NEGOTIATE_AUTHENTICATION</h5>
<ul>
  <b>Description:&nbsp;</b>If set to true enables the HTTP Negotiate
     authentication method,  as described by RFC 4559, both to Pegasus server
     and client.

     Enabling this option also adds 1) a new option to the runtime
     configuration variable "httpAuthType" and 2) a new runtime variable
     "mapToLocalName". <br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Value (Development Build):&nbsp;</b>false<br>
  <b>Recommended Value (Release Build):&nbsp;</b>false<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>HTTP Negotiate support requires the GSSAPI
     development headers and libraries to build OpenPegasus, such as
     libgssapi_krb5 from MIT Kerberos5 implementation.<br>
</ul>

<h5>PEGASUS_PLATFORM</h5>
<ul>
  <b>Description:&nbsp;</b>Describes the target platform for the
     build.  The list of supported values for this variable
     is defined in pegasus/mak/config.mak.&nbsp; Please refer to
     that file for a complete list of valid PEGASUS_PLATFORM
     values.&nbsp; This document includes platform-specific configuration
     data for only a subset of the supported platforms.&nbsp; The
     following table describes the platforms documented in
     this version of the document. <br>
  <b>Default Value:&nbsp;</b>None<p>&nbsp;</p>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="542">
       <tbody><tr>
        <th bgcolor="#cae6ca" width="190">Platform</th>
        <th bgcolor="#cae6ca" width="351">Recommended Value <br>
          Development Build</th>
        <th bgcolor="#cae6ca" width="338">Recommended Value <br>
          Release Build</th>
       </tr>
       <tr align="center">
        <td align="left" width="190">Linux IA32</td>
        <td width="351">LINUX_IX86_GNU</td>
        <td width="338">LINUX_IX86_GNU</td>
      </tr>
      <tr align="center">
       <td align="left" width="190">Linux IA64</td>
       <td width="351">LINUX_IA64_GNU</td>
       <td width="338">LINUX_IA64_GNU</td>
      </tr>
      <tr align="center">
       <td align="left" width="190">Linux X86_64</td>
       <td width="351">LINUX_X86_64_GNU</td>
       <td width="338">LINUX_X86_64_GNU</td>
      </tr>
      <tr align="center">
       <td align="left" width="190">HP-UX PA-RISC</td>
       <td width="351">HPUX_PARISC_ACC</td>
       <td width="338">HPUX_PARISC_ACC</td>
      </tr>
      <tr align="center">
       <td align="left" width="190">HP-UX IPF</td>
       <td width="351">HPUX_IA64_ACC</td>
       <td width="338">HPUX_IA64_ACC</td>
      </tr>
      <tr align="center">
       <td align="left" width="190">OpenVMS Alpha</td>
       <td width="351">VMS_ALPHA_DECCXX</td>
       <td width="338">VMS_ALPHA_DECCXX</td>
      </tr>
      <tr align="center">
       <td align="left" width="190">OpenVMS IA64</td>
       <td width="351">VMS_IA64_DECCXX</td>
       <td width="338"> VMS_IA64_DECCXX</td>
      </tr>
     </tbody></table>
     <br><br>
  <b>Required:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>The error "PEGASUS_PLATFORM
     environment variable undefined." is returned if the
     PEGASUS_PLATFORM environment variable is not set.
</ul>

<h5>PEGASUS_REMOVE_METHODTRACE</h5>
<ul>
  <b>Description:&nbsp;</b>If true, the CIM Server is compiled without
     method enter and exit trace statements.&nbsp; Trace Level 5 will
     continue to be accepted as a valid trace level but, without the
     method enter and exit trace statements, it will be equivalent to
     Trace Level 4. If PEGASUS_REMOVE_METHODTRACE is false or not set,
     method enter and exit trace statements are included.&nbsp; All
     other values are considered invalid and will result in a build
     error.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set (The
     Considerations section gives guidance on when a different
     decision would be made.)<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set (The
     Considerations section gives guidance on when a different
     decision would be made.)<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This option completely removes the
     method enter/exit trace statements from the generated object code.
     It defines the PEG_METHOD_ENTER and PEG_METHOD_EXIT macros
     to null statements. This helps to keep static code size small
     but reduces the serviceability of the CIM server.<br>
</ul>


<h5>PEGASUS_REPOSITORY_MODE</h5>
<ul>
  <b>Description:&nbsp;</b>This variable defines the default mode
     used to create repositories that are constructed as part of the
     automated build tests.&nbsp; It does not affect the runtime
     environment. Valid values include: XML (causes
     the repository to be built in XML mode); BIN (causes
     the repository to be built in binary mode). Use cimconfig to
     modify the runtime environment.<br>
  <b>Default Value:&nbsp;</b>XML<br>
  <b>Recommended Value (Development Build):&nbsp;</b>XML<br>
  <b>Recommended Value (Release Build):&nbsp;</b>XML<br>
  <b>Required:&nbsp;</b>No<p>&nbsp;</p>
</ul>

<h5>PEGASUS_REPOSITORY_STORE_COMPLETE_CLASSES</h5>
<ul>
  <b>Description:&nbsp;</b>This variable defines the default contents of a
     class definition in the repository store when a new repository is created.
     Specifically, when set to true, propagated elements are included in a
     class definition in the persistent store.  The contents of a class
     definition returned from the repository interface is not affected by this
     option.<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Value (Development Build):&nbsp;</b>false<br>
  <b>Recommended Value (Release Build):&nbsp;</b>false<br>
  <b>Required:&nbsp;</b>No<p>&nbsp;</p>
  <b>Considerations:&nbsp;</b>A repository which stores complete class
     definitions does not allow modifications to non-leaf classes or changes
     to a superclass designation.  Complete classes use more storage space,
     often twice as much as local (incomplete) classes.  Class retrieval may
     be more expensive when local classes are stored.  No specific mechanism
     is available to change this setting in an existing repository.<br>
</ul>

<h5>PEGASUS_SLP_REG_TIMEOUT</h5>
<ul>
  <b>Description:&nbsp;</b>Most SLP implementations allow a lifetime
     value to be specified in the registration sent to the SLP SA or
     DA. The PEGASUS_SLP_REG_TIMEOUT build variable allows a lifetime
     (ie. timeout) value to be specified on the SLP registration, with
     a 're-registration' being sent to SLP at the same specified
     timeout interval. The purpose of this lifetime or timeout value
     is to avoid the accumulation of stale service information
     in the SA or DA.<br>
  <b>Default Value:&nbsp;</b>Undefined<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Undefined<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Undefined<br>
  <b>Required:&nbsp;</b>No<p><b>Example: </b>
     PEGASUS_SLP_REG_TIME=1440 (ie. 24 hours or 1 day)<br>
  <b>Considerations:&nbsp;</b>(1) The OpenPegasus internal SLP
     implementation does not support timeout registrations. This
     build option is useful, for example, if PEGASUS_USE_OPENSLP is
     defined. (2) Some SLP implementations may impose a
     maximum value for the lifetime parameter. For example, OpenSLP
     limits this value to SLP_LIFETIME_MAXIMUM (or 0xFFFF), and
     if this maximum value is passed to OpenSLP, then the timeout
     feature is disabled. Refer to the documentation of your SLP
     implementation for more information. (3) OpenPegasus will not
     do any validity checking on the specified value, either
     to determine if it is a valid positive integer or if it
     exceeds some maximum value.<br>
</p></ul>

<h5>PEGASUS_SNIA_EXTENSIONS</h5>
<ul>
  <b>Description:&nbsp;</b> This variable is used to enable a
     set of workarounds that support the use of OpenPegasus
     in the SNIA Test Environment.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>The functionality enabled with this
     variable is experimental and subject to change.
</ul>

<h5>PEGASUS_SKIP_MOST_TEST_DIRS</h5>
<ul>
  <b>Description:&nbsp;</b>If set to true, this variable can be used
     to reduce the time required to build OpenPegasus by significantly
     reducing the number of tests that are built.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Setting this variable to true
     affects the behavior of all recursive make targets (e.g.,
     clean, depend, all, unittests, alltests, and slptests).
     Use of this variable with test-related targets (e.g., unittests,
     alltests and slptests) can produce unexpected results.
     To avoid creating an inconsistent PEGASUS_HOME directory,
     the PEGASUS_HOME directory (i.e., the OpenPegasus build
     directory) should be removed prior to enabling or disabling
     this variable. This variable should not be used to characterize
     the set of files to be packaged in a release build. Please
     refer to the Runtime Packaging Definition PEP for the release
     for a recommended list of files to be included in a release.
</ul>

<h5>PEGASUS_TEST_ENABLE_DEBUG_TRACE</h5>
<ul>
  <b>Description:&nbsp;</b>
     This variable is only used for testing. If set to true,
     Discarded data trace will be enabled by the install_run
     target of the src/Server/Makefile before running the
     OpenPegasus TestMakefile test suite. <br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>
     This variable is useful in certain test environments to
     explicitly enable tracing to aid in better troubleshooting and
     detection of test failures (E.g. Test systems are experiencing
     test failures due to connection timeouts, lost indications
     etc).<br>	
</ul>

<h5>PEGASUS_TEST_ISGROUP_GROUP/PEGASUS_TEST_ISGROUP_USER_SUCCESS/PEGASUS_TEST_ISGROUP_USER_FAILURE</h5>
<ul>
  <b>Description:&nbsp;</b>These variables are only used for testing.
     These variables allow the developer to define a valid group name,
     PEGASUS_TEST_ISGROUP_GROUP, a valid user name that is in the
     group, PEGASUS_TEST_ISGROUP_USER_SUCCESS, and an a valid user
     name that is not in the group, PEGASUS_TEST_ISGROUP_USER_FAILURE.
     These variables are only used for testing and NOT part of the
     release.<br>
  <b>Default Value(Windows):</b>
     Administrator/Administrators/Guest<br>
  <b>Default Value(Non-Windows):&nbsp;</b>root/root/guest<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Used<br>
  <b>Required:&nbsp;</b>No
</ul>

<h5>PEGASUS_TEST_IPV6</h5>
<ul>
  <b>Description:&nbsp;</b>This variable is only used for
     testing.&nbsp; If set to true, the IPv6-specific tests will
     be run as part of the "alltests" OpenPegasus
     TestMakefile test suite. If this variable is not set or set to
     false,&nbsp; the IPv6-specific tests will not be run.&nbsp; All
     other values are invalid.<br>
  <b>Default Value:&nbsp; </b>If PEGASUS_TEST_IPV6 is not defined,
     PEGASUS_TEST_IPV6 is set to the value of PEGASUS_ENABLE_IPV6.<br>
  <b>Recommended Value (Development Build): </b>Set to the value
     of PEGASUS_ENABLE_IPV6<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Used<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This variable is useful in certain
     test environments to explicitly disable running the IPv6
     tests (e.g., when running an IPv6-enabled version of
     OpenPegasus on an an IPv4 system).<br>
</ul>

<h5>PEGASUS_TEST_SDK</h5>
<ul>
  <b>Description:&nbsp;</b>This variable is only used for
     testing.&nbsp; It is used to control testing of the SDK
     sample providers and clients. If set, the setup, building and
     testing of the SDK samples is enabled as part of the
     OpenPegasus automated build and test.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Used<br>
  <b>Required:&nbsp;</b>No
</ul>
	
<h5>PEGASUS_TEST_USER_DEFINED</h5>
<ul>
  <b>Description:&nbsp;</b>This variable is only used for testing.
     If this variable is set, the tests will assume that the
     PEGASUS_TEST_USER_ID and PEGASUS_TEST_USER_PASS variables
     defines a valid user/password pair and can be used for
     certificate-based authentication testing.&nbsp; These tests
     also assumes that "invalidUser" is not a valid
     user.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Used<br>
  <b>Required:&nbsp;</b>No
</ul>

<h5>PEGASUS_TEST_USER_ID/PEGASUS_TEST_USER_PASS</h5>
<ul>
  <b>Description:&nbsp;</b>These variables are only used for
     testing. These variables allow the developer to define a
     valid, non-privileged&nbsp; user name and password
     on the test system that can be used as part of the OpenPegasus
     automated test scripts to perform authentication and
     authorization testing.&nbsp; These variables are only used for
     testing and NOT part of the release.<br>
  <b>Default Value:&nbsp;</b>guest/guest<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Used<br>
  <b>Required:&nbsp;</b>No<br>
</ul>

<h5>PEGASUS_TEST_VALGRIND_LOG_DIR</h5>
<ul>
  <b>Description:&nbsp;</b>
     This variable is currently only supported on Linux. It may be
     set to run regression tests under the
     <a href="http://www.valgrind.org/">Valgrind</a> memory
     checking tool. It must specify a directory for writing
     Valgrind log files. The file name format for a particular
     log is PEGASUS_TEST_VALGRIND_LOG_DIR/PROGRAM_NAME.pid.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This flag is only supported on Linux to
     enable running tests under Valgrind.<br>
</ul>

<h5>PEGASUS_TMP</h5>
<ul>
  <b>Description:&nbsp;</b>This variable is only used in a test
     environment. It can be used to define the directory that
     OpenPegasus test programs should use to store temporary files.<br>
  <b>Default Value:&nbsp;</b>"."<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Used<br>
  <b>Required:&nbsp;</b>No<br>
</ul>
	
<h5>PEGASUS_USE_DEBUG_BUILD_OPTIONS</h5>
<ul>
  <b>Description:&nbsp;</b>The PEGASUS_DEBUG flag is used to control
     a variety of settings, including compile options, assertion
     enablement, method definitions for testing, and diagnostic
     output.&nbsp; The PEGASUS_USE_DEBUG_BUILD_OPTIONS variable
     can be used to enable just the compiler specific debug options
     (e.g., -g in g++) .<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This variable is automatically set
     if PEGASUS_DEBUG is set.<br>
</ul>

<h5>PEGASUS_USE_EMANATE</h5>
<ul>
  <b>Description:&nbsp;</b>EMANATE,
     <a href="http://www.snmp.com/products/emanate.html">
     http://www.snmp.com/products/emanate.html</a>, is an SNMP Research
     International product that supports SNMPv1, SNMPv2c, and
     SNMPv3.&nbsp; If the PEGASUS_USE_EMANATE variable is defined,
     the OpenPegasus SNMP Handler will use the EMANATE libraries
     to send traps to the SNMP Management application.&nbsp;
     The EMANATE libraries are NOT included as part of OpenPegasus.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<p>
  <b>Considerations:&nbsp;</b>Either the PEGASUS_USE_NET_SNMP or
     PEGASUS_USE_EMANATE variable must be set for the SNMP
     Handler to be supported.<br>
</p></ul>


<h5>PEGASUS_USE_NET_SNMP</h5>
<ul>
  <b>Description:&nbsp;</b>NET-SNMP,
     <a href="http://net-snmp.sourceforge.net">
     http://net-snmp.sourceforge.net</a>,&nbsp; is an OSS
     implementation of a suite of applications used to implement
     <a href="http://www.ietf.org/rfc/rfc1157.txt">SNMP v1</a>,
     <a href="http://www.ietf.org/rfc/rfc1901.txt">SNMP v2c</a> and
     <a href="http://www.ietf.org/rfc/rfc2571.txt">SNMP v3</a> using
     both IPv4 and IPv6.&nbsp;&nbsp; If the PEGASUS_USE_NET_SNMP
     variable is defined, the OpenPegasus SNMP Handler will use
     the NET-SNMP libraries to send traps to the SNMP Management
     application.&nbsp; The NET-SNMP libraries are NOT included
     as part of OpenPegasus.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true for Linux,
     false for all other platforms<br>
  <b>Required:&nbsp;</b>No<p>
  <b>Considerations:&nbsp;</b>Either the PEGASUS_USE_NET_SNMP or
     PEGASUS_USE_EMANATE variable must be set for the SNMP
     Handler to be supported.<br>
</p></ul>

<h5>PEGASUS_ENABLE_NET_SNMPV3</h5>
<ul>
  <b>Description:&nbsp;</b>If this variable is defined,
     then OpenPegasus SNMP Handler will build the SNMPV3 
     features. This should be set to false if NET-SNMP 5.2 and lower 
     libraries are used.<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true<br>
  <b>Required:&nbsp;</b>No<p>
  <b>Considerations:&nbsp;</b>PEGASUS_USE_NET_SNMP variable must 
     be set.<br>
</p></ul>


<h5>PEGASUS_USE_OPENSLP</h5>
<ul>
  <b>Description:&nbsp;</b>OpenSLP, <a href="http://www.openslp.org">
     http://openslp.org</a>, is an open-source implementation of
     Service Location Protocol. If the PEGASUS_USE_OPENSLP variable
     is defined, OpenPegasus will be built to use the OpenSLP
     implementation of SLP instead of the internal OpenPegasus
     implementation of SLP. The OpenSLP libaries are NOT included
     as part of OpenPegasus.
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>PEGASUS_ENABLE_SLP must be defined
     if this variable is set.
</ul>

<h5>PEGASUS_USE_PAM_STANDALONE_PROC</h5>
<ul>
  <b>Description:&nbsp;</b>Moves the processing of PAM requests from
     the CIM Server process to a separate process managed by the
     CIM Server.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>If PAM Authentication is enabled,
     the PAM API is used, during the processing of each request, to
     authenticate the client.  This level of use makes the CIM Server
     extremely sensitive to memory leaks in the PAM library.  In
     addition, certain PAM modules are not thread-safe.  If your
     platform is experiencing problems with PAM Authentication,
     use of option may provide a work-around.
     PEGASUS_USE_PAM_STANDALONE_PROC requires
     PEGASUS_PAM_AUTHENTICATION to be set.<br>
</ul>

<h5>PEGASUS_USE_RELEASE_CONFIG_OPTIONS</h5>
<ul>
  <b>Description:&nbsp;</b>If set, OpenPegasus is built using
     the "Release Build" configuration options. By default,
     OpenPegasus is built using the "Development Build"
     configuration options.<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Value (Development Build):&nbsp;</b>false<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>(1)The
     PEGASUS_USE_RELEASE_CONFIG_OPTIONS variable allows a platform
     vendor to easily toggle between two sets of configurations
     options, a set of options tuned for the development/debug
     ("Development Build") environment and a set of options
     tuned for the production environment ("Release Build").
     Refer the section titled "Configuration Properties" for
     additional detail.&nbsp; (2) For each configuration
     variable,&nbsp; the "Recommended Value (Release Build)"
     value defines the recommended settings to use for a
     "Release Build".&nbsp; Please refer to the
     description of each variable for additional information.
</ul>

<h5>PEGASUS_USE_RELEASE_DIRS</h5>
<ul>
  <b>Description:&nbsp;</b>If set, OpenPegasus is built using
     the "Release Build" directory definitions. By default,
     OpenPegasus is built using the "Development Build"
     directory definitions.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>
     The PEGASUS_USE_RELEASE_DIRS variable allows a platform
     vendor to easily toggle between two sets of directory
     definitions, a set tuned for the development/debug
     ("Development Build") environment and a set tuned for the
     production environment ("Release Build").  Refer the section
     titled "Configuration Properties" for additional detail.<br>
</ul>

<h5>PEGASUS_FLAVOR</h5>
<ul>
  <b>Description:&nbsp;</b> This variable is used for configuring Multi CIMOM 
     on same OS by eliminating single point for storage of PID's and configuration
     files. Flavor is used in structuring the release dirs,configuration file names,
     log identity and PAM config file.
     If set, OpenPegasus is built using the flavor value. By default OpenPegasus is
     built using "tog" as the flavor. RPMs are named using the flavor value.
  <br>
  <b>Default Value:&nbsp;</b>tog<br>
  <b>Recommended Value (Development Build):&nbsp;</b>tog<br>
  <b>Recommended Value (Release Build):&nbsp;</b>tog<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>
     To build RPM using flavor, RPM spec file needs to be regenerated after setting the flavor value.
     This can be done using the create_OpenPegasusRPMSpecFile target in the Makefile.Release.
     Platforms have to define their own release dir structure using the flavor for release builds.
     An error will be reported if both PEGASUS_FLAVOR and PEGASUS_USE_RELEASE_DIRS are set and
     PEGASUS_OVERRIDE_DEFAULT_RELEASE_DIRS is not set.
     RPM build on linux defines PEGASUS_OVERRIDE_DEFAULT_RELEASE_DIRS by default.
  <br>
</ul>

<h5>PEGASUS_PLATFORM_FOR_32BIT_PROVIDER_SUPPORT</h5>
<ul>
  <b>Description:&nbsp;</b> Builds the Pegasus with 32-bit provider support for the specified platform.
    If this option is set, the value MUST be one of the 32-bit supported platforms by Pegasus.
  <br>
  <b>Default Value:&nbsp;</b>Not set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Not set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>
     This option is used to run the 32-bit providers under 64-bit CIMserver.
     To register the 32-bit providers, register the provider module by setting the
     Bitness property value to "2". 32-bit Providers are always loaded out of process
     irrespective of forceProviderProcesses config option.
  <br>
</ul>

<h5>PEGASUS_USE_SQLITE_REPOSITORY</h5>
<ul>
  <b>Description:&nbsp;</b>If true, new repository stores are created
     using a SQLite database.  Existing file-based stores will continue
     to be recognized and operate seamlessly.<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Value (Release Build):&nbsp;</b>true<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>If PEGASUS_USE_SQLITE_REPOSITORY is set to true
     and SQLite files are not installed in default search locations,
     SQLITE_HOME must also be configured.
     PEGASUS_REPOSITORY_STORE_COMPLETE_CLASSES may not be set to true when
     PEGASUS_USE_SQLITE_REPOSITORY is set to true.
</ul>

<h5>PEGASUS_USE_SYSLOGS</h5>
<ul>
  <b>Description:&nbsp;</b>If set, OpenPegasus will be built
     to send log messages to the system logger (syslog).
     Otherwise, log messages will be sent to OpenPegasus
     specific log files.<br>
  <b>Recommended Value (Development Build):&nbsp;</b>Set<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This variable is currently
     not implemented as an environment variable. To use
     the option -DPEGASUS_USE_SYSLOGS must
     be explicitly included in the appropriate platform
     makefile (pegasus/mak/platform_*.mak).</ul>

<h5>PEGASUS_WINDOWS_SDK_HOME</h5>
<ul>
  <b>Description:&nbsp;</b>This variable should be set to point
     to the Microsoft Platform SDK on Windows if using a compiler
     version &lt; 1300 (i.e. VC6). If using VC7 or VC8, this flag
     does not need to be set, as the necessary libraries are already
     included.<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>Yes, if building on Windows with a
     compiler version &lt; 1300.<br>
</ul>

<h5>SQLITE_HOME</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the SQLite SDK directory.
     This directory must contain sqlite3.h in the $(SQLITE_HOME)/include
     directory, and libsqlite3 in the $(SQLITE_HOME)/lib directory.<br>
  <b>Default Value:&nbsp;</b>Not Set<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Recommended Value (Release Build):&nbsp;</b>
     No Specific Recommendation<br>
  <b>Required:&nbsp;</b>Yes, if PEGASUS_USE_SQLITE_REPOSITORY is set to true
     and the SQLite files are not installed in locations that are searched by
     default.<br>
  <b>Considerations:&nbsp;</b>This environment variable is only used if
     PEGASUS_USE_SQLITE_REPOSITORY is set to true.
</ul>

<h5>PEGASUS_INITIAL_THREADSTACK_SIZE</h5>
<ul>
  <b>Description:&nbsp;</b>This environment variable sets the initial size 
     of the stack on new threads. Value is specified in number of bytes.<br>
  <b>Default Value:&nbsp;</b>262144<br>
  <b>Recommended Value (Development Build):&nbsp;</b>262144<br>
  <b>Recommended Value (Release Build):&nbsp;</b>262144<br>
  <b>Required:&nbsp;</b>No <p></p>
</ul>

<h4>Examples Building a Linux IA32 (#IA64) Development/Debug Version</h4>
<ul>
  export PEGASUS_ROOT=/home/pegasusbld/pegasus<br>
  export PEGASUS_HOME=/home/pegasusbld/pegasus/build<br>
  export PEGASUS_PLATFORM=LINUX_IX86_GNU<br>
  #export PEGASUS_PLATFORM=LINUX_IA64_GNU<br>
  export PEGASUS_PAM_AUTHENTICATION=true<br>
  export PEGASUS_USE_PAM_STANDALONE_PROC=true<br>
  export PEGASUS_HAS_SSL=yes<br>
  export PEGASUS_DEBUG=TRUE<br>
  export ENABLE_CMPI_PROVIDER_MANAGER=true<br>
  export PEGASUS_USE_SYSLOGS=true<br>
  export PATH=/home/pegasusbld:/home/pegasusbld/pegasus/build/bin:/usr/local/bin:$PATH<br>
</ul>

<h4>Building a Linux IA32 (#IA64) Production Release Version</h4>
<ul>
  export PEGASUS_ROOT=/home/pegasusbld/pegasus<br>
  export PEGASUS_HOME=/home/pegasusbld/pegasus/build<br>
  export PEGASUS_PLATFORM=LINUX_IX86_GNU<br>
  #export PEGASUS_PLATFORM=LINUX_IA64_GNU<br>
  export PEGASUS_ENABLE_CQL=false<br>
  export PEGASUS_PAM_AUTHENTICATION=true<br>
  export PEGASUS_USE_PAM_STANDALONE_PROC=true<br>
  export PEGASUS_HAS_SSL=yes<br>
  export PEGASUS_USE_RELEASE_CONFIG_OPTIONS=true<br>
  export PEGASUS_USE_RELEASE_DIRS=true<br>
  export PEGASUS_NOASSERTS=true<br>
  export ENABLE_CMPI_PROVIDER_MANAGER=true<br>
  export PEGASUS_ENABLE_USERGROUP_AUTHORIZATION=true<br>
  export PEGASUS_USE_SYSLOGS=true<br>
  export PATH=/home/pegasusbld:/home/pegasusbld/pegasus/build/bin:/usr/local/bin:$PATH<br>
</ul>

<h3>Environment Variable Settings for <u>Running</u> OpenPegasus</h3>

<h4>Definitions</h4>

<h5>PEGASUS_HOME</h5>
<ul>
  <b>Description:&nbsp;</b>There are multiple options for
     configuring the location of OpenPegasus runtime
     files (e.g., configuration files, libraries,
     repository, executables).  If no other option is
     specified, OpenPegasus will attempt to use the value
     PEGASUS_HOME.<br>
  <b>Default Value:&nbsp;</b>"."<br>
  <b>Recommended Value (Development Build):&nbsp;</b>
     The same value defined at build time.<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set<br>
  <b>Required:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Although this variable can be
     useful in a development environment use of this environment
     variable is not recommended in a production environment.
     Instead, the use of configuration properties to explicitly
     set the location of runtime files and directories is recommended.
</ul>

<h5>PEGASUS_MSG_HOME</h5>
<ul>
  <b>Description:&nbsp;</b>This value is not used by the CIM
     Server.&nbsp; The CIM Server uses the messageDir configuration
     parameter to locate the directory where the ICU resource bundles.
     However, CIM Client applications must rely on an alternative
     mechanism to locate this directory.<br>
  <b>Default Value:&nbsp;</b>if $PEGASUS_HOME is set then
     "$PEGASUS_HOME/msg" else "."<br>
  <b>Recommended Value (Development Build): </b>$PEGASUS_HOME/msg<br>
  <b>Recommended Value (Release Build):&nbsp;</b>Not Set <br>
  <b>Required:&nbsp;</b>No<br>
</ul>

<h3>Configuration Properties</h3>

<h4>Notation</h4>

<p>This section describes the notation used to define the
configuration properties.</p>

<ul>

<h5>Default Value</h5>
    The value of <i>Default Value</i> is the OpenPegasus
    default setting for this configuration option.  This
    value is used if a platform-specific setting is not
    defined.

<h5>Recommended Default Value</h5>
    The PEGASUS_USE_RELEASE_CONFIG_OPTIONS variable allows a
    platform vendor to easily toggle between two sets of
    configurations options, a set of options tuned for the
    development/debug ("Development Build") environment
    and a set of options tuned for the production environment
    ("Release Build"). The value of
    <i>Recommended Value (Development Build)</i>
    is the recommended default value for use in a development/
    debug environment.  The value of
    <i>Recommended Value (Release Build)</i> is the recommended
    default value for use in a production environment.

<h5>Recommend To Be Fixed/Hidden</h5>
    Configuration options can be defined as fixed or hidden.
    A "fix" configuration option is set at build time
    and cannot be changed without rebuilding. "Fixed"
    configuration options are not displayed using the cimconfig
    command.  This feature can be used by vendors to limit
    OpenPegasus functionality and configurability.

    A "hidden" configuration option is an option that is
    configurable (i.e., "not fixed"), but not externally
    advertised using the cimconfig command.  The "hidden"
    feature can be used to define "internal use only"
    configuration options.

<h5>Dynamic?</h5>
    If yes, the value of the configuration option can be
    changed without stopping and restarting the CIM Server.

<h5>Directory Specifications</h5>
    <p>Note that the variables included in the following table
    (e.g., $LOGDIR) are for documentation purposes only and
    have been defined to simplify the description of the
    configuration options.&nbsp; In particular,
    these variables DO NOT correspond to environment variables
    implemented in the OpenPegasus code.&nbsp; Default values
    for the following variables are platform
    and vendor dependent and not documented in this document.</p>

    <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" height="228" width="148">
      <tbody><tr>
        <th bgcolor="#cae6ca" height="16" width="1">&nbsp;</th>
      </tr>
        <tr align="center">
        <td align="left" height="12" width="1">$LOGDIR</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$PROVIDERDIRS</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">
          $PROVIDERMANAGERDIRS</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$REPOSITORYDIR </td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$CERTIFICATEDIR&nbsp;
        </td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$LOCALAUTHDIR</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$TRACEDIR</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$CONFIGDIR</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$PIDFILE</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$RANDOMDIR</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$SOCKETDIR</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$MESSAGEDIR</td>
      </tr>
      <tr align="center">
        <td align="left" height="14" width="1">$WEBCONFDIR</td>
      </tr>

      </tbody></table>
</ul>

<h4>Definitions</h4>

<h5>authorizedUserGroups</h5>
<ul>
  <b>Description:</b>&nbsp;If the <b>authorizedUserGroups</b>
     property is set, the value is interpreted as a list of
     comma-separated user groups whose members may issue CIM
     requests. A user who is not a member of any of these groups is
     restricted from issuing CIM requests, with the exception of
     privileged users (root user). If the <b>authorizedUserGroups</b>
     property is not set, any user may issue CIM requests.<br>
  <b>Default Value:&nbsp;</b>blank<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>blank<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>blank<br>
  <b>Recommend To Be Fixed/Hidden (Development Build):&nbsp;</b>
     No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Example: </b>
     #cimconfig -s authorizedUserGroups=users,systemusers -p<br>
  <b>Considerations:&nbsp;</b>This feature is available only when
     the OpenPegasus source is compiled with the flag
     PEGASUS_ENABLE_USERGROUP_AUTHORIZATION set.
</ul>

<h5>daemon</h5>
<ul>
  <b>Description:&nbsp;</b>This option enables/disables forking of
     the code to create a background daemon process.<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>true<br>
  <b>Recommend To Be Fixed/Hidden (Development Build):&nbsp;</b>
     No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>
     No/Yes<br>
  <b>Dynamic?:&nbsp;</b>No<p>&nbsp;<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
     <tbody><tr>
       <th bgcolor="#cae6ca" width="168">Platform</th>
       <th bgcolor="#cae6ca" width="350">Source Configuration File</th>
     </tr>
     <tr align="center">
       <td width="168">Linux</td>
       <td align="left" width="350">
         Pegasus/Config/DefaultPropertyTableLinux.h</td>
     </tr>
     <tr align="center">
       <td width="168">HP-UX</td>
       <td align="left" width="350">
         Pegasus/Config/DefaultPropertyTableHpux.h</td>
     </tr>
     <tr align="center">
       <td width="168">OpenVMS</td>
       <td align="left" width="350">
         Pegasus/Config/DefaultPropertyTableVms.h</td>
     </tr>
     </tbody></table>
</p></ul>

<h5>enableAssociationTraversal</h5>
<ul>
  <b>Description:&nbsp;</b>If true, the CIM Server will support
     the four association traversal operators: Associators,
     AssociatorNames,References, and ReferenceNames.<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>true<br>
  <b>Recommend To Be Fixed/Hidden (Development Build):&nbsp;</b>
     No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>There is still an outstanding
     Provider Registration issue that restricts the degree to
     which separate Providers can register for Associations.<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
     <tbody><tr>
       <th bgcolor="#cae6ca" width="168">Platform</th>
       <th bgcolor="#cae6ca" width="350">Source Configuration File</th>
     </tr>
     <tr align="center">
       <td width="168">Linux</td>
       <td align="left" width="350">
         Pegasus/Config/DefaultPropertyTableLinux.h</td>
     </tr>
     <tr align="center">
       <td width="168">HP-UX</td>
       <td align="left" width="350">
         Pegasus/Config/DefaultPropertyTableHpux.h</td>
     </tr>
     <tr align="center">
       <td width="168">OpenVMS</td>
       <td align="left" width="350">
         Pegasus/Config/DefaultPropertyTableVms.h</td>
     </tr>
     </tbody></table>
</ul>

<h5>enableAuditLog</h5>
<ul>
  <b>Description:&nbsp;</b>Used to enable or disable audit
     logging at run time. If true, audit logging will be enabled.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>false<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build):&nbsp;</b>
     No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/DefaultPropertyTable.h<br>
</ul>

<h5>enableAuthentication</h5>
<ul>
  <b>Description:&nbsp;</b>If true, a Client must be authenticated
     to access the CIM Server.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>false<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>true<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp<br>
</ul>

<h5>enableBinaryRepository</h5>
<ul>
  <b>Description:&nbsp;</b>Setting this to true will activate the
     binary repository support on the next restart of cimserver.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>false<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build):&nbsp;</b>Yes<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Repositories containing a mixture
     of binary and XML objects are supported.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/RepositoryPropertyOwner.cpp<p></p>
</ul>


<h5>enableHttpConnection</h5>
<ul>
  <b>Description:&nbsp;</b>If true, allows connections to
     the CIM Server using the HTTP protocol<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>
     Enabling HTTP will allow clients to connect with security
     properties different than those associated with encrypted SSL
     traffic, and its configured SSL authentication or other security
     behavior. This option should only be enabled in environments
     where sending the HTTP Request and HTTP Response as
     clear text messages does not introduce a security risk.&nbsp;
     Note that if authentication is enabled (enableAuthentication),
     user names and passwords will be included in the text of the
     HTTP message.<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h5>enableHttpsConnection</h5>
<ul>
  <b>Description:&nbsp;</b>If true, allows connections to
     the CIM Server using the HTTPS protocol (HTTP using
     Secure Socket Layer encryption)<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>true<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>For this option to work,
     the environment variable PEGASUS_HAS_SSL must have
     been set when CIM Server was built.<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
          Pegasus/Config/DefaultPropertyTableLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
          Pegasus/Config/DefaultPropertyTableHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
          Pegasus/Config/DefaultPropertyTableVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h5>enableIndicationService</h5>
<ul>
  <b>Description:&nbsp;</b>If true, the CIM Server will support
     CIM Indications.<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>true<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>Yes/No<br>
  <b>Considerations:&nbsp;</b>When enableIndicationService is set to
     false dynamically, delete subscription requests are sent to all
     indication providers and indication related operations are
     not supported until indication service is re-enabled. Dynamic
     configuration facility is available only when Pegasus is compiled
     with PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT=true. Clients
     who wants to utilize the IndicationService services MUST check for
     CIM_IndicationService EnabledState and HealthState properties to know
     the current indication service state. For example, User can enumerate
     instances of CIM_IndicationService and there is exactly one instance
     of CIM_IndicationService returned. (Ex. using cimcli command
     'cimcli ei -n root/PG_InterOp CIM_IndicationService'). When requested state
     change(Enabled/Disabled) cannot be made because of timeout or some
     other exception IndicationService HealthState is set to "Degraded/Warning".
     For example, if user requested for indication service disable (by setting
     enableIndicationService=false), disable failed because of timeout or some
     other exception. Now service health state is set to "Degraded/Warning"
     and service EnabledState will remain enabled. User can now identify the
     faulty provider causing the timeout or any other problem and can take
     appropriate action. User can again request for service disable to recover
     from degraded state. Similar sequence applies while enabling the indication
     service. Only difference is that service EnabledState is set to Enabled
     if exception or timeout happens. There is no automatic recovery from 
     degraded state is available at present.<br>
  <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h5>enableNamespaceAuthorization</h5>
<ul>
  <b>Description:&nbsp;</b>If true, the CIM Server restricts
     access to namespaces based on configured user authorizations
     [user authorizations may be configured using the cimauth
     command]<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Default Value (Development Build): </b>false<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>
     This option offers limited functionality and, in most
     environments, expensive to administer.  It's use is not
     recommended.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp</ul>

<h5>enableNormalization</h5>
<ul>
  <b>Description:&nbsp;</b>If true, objects returned from instance
     providers are validated and normalized. <br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>
    <ul>
      <li>Any errors encountered during normalization result in a
          CIMException with the status code set to CIM_ERR_FAILED
          and a meaningful, context specific error description
          (messages will be localized). Providers that catch the
          exception have an opportunity to handle the error.
          Otherwise, the exception is passed to the Provider Manager
          and becomes the response for that Provider.
      </li><li>Provider Modules that are listed on the
          excludeModulesFromNormalization
          configuration option are excluded from normalization.
      </li><li>Since the concept of normalization is relatively new to
          OpenPegasus and it establishes and enforces rules for
          objects returned by providers, it should only
          apply to providers written against the SDK in which it was
          introduced (or later). Therefore only Provider Modules that
          have the following InterfaceType and InterfaceVersion
          combination will be subject to normalization:
        <ul>
            <li>'C++Default' / 2.5.0 or greater
            </li><li>'CMPI' / 2.0.0 or greater
            </li><li>'JMPI' / 1.0.0 or greater
        </li></ul>
     </li></ul>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/NormalizationPropertyOwner.cpp<br>
</ul>


<h5>enableRemotePrivilegedUserAccess</h5>
<ul>
  <b>Description:&nbsp;</b>If true, the CIM Server allows
     access by a privileged user from a remote system<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>true<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Many management operations require
     privileged user access.  Disabling remote access by
     privileged user could significantly affect
     functionality.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp<p>&nbsp;</p>
</ul>

<h5>enableSubscriptionsForNonprivilegedUsers</h5>
<ul>
  <b>Description:&nbsp;</b>If true, operations (create instance,
     modify instance, delete instance, get instance, enumerate
     instances, enumerate instance names) on indication
     filter, listener destination, and subscription instances
     may be performed by non-privileged users. Otherwise, these
     operations may only be performed on these instances by
     privileged users.<br>
  <b>Default Value:&nbsp;</b>true<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This option has meaning only if
     enableIndicationService=true.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp<p>&nbsp;</p>
</ul>

<h5>excludeModulesFromNormalization</h5>
<ul>
  <b>Description:&nbsp;</b>If the excludeModulesfromNormalization
     property is set, the value is interpreted as a list of
     comma-separated Provider Module names (as specified in
     PG_ProviderModule.Name) to exclude from validation and
     normalization.<br>
  <b>Default Value:&nbsp;</b>""<br>
  <b>Recommended Default Value (Development Build):</b>
     ""<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     ""<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>All objects managed by all
     providers will be excluded from validation and normalization
     if its module name appears in this list.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/NormalizationPropertyOwner.cpp
</ul>

<h5>forceProviderProcesses</h5>
<ul>
  <b>Description:&nbsp;</b>If true, the CIM Server runs Providers
     in separate processes rather than loading and calling Provider
     libraries directly within the CIM Server process.<br>
  <b>Default Value:&nbsp;</b>Dependent on the value of
     PEGASUS_DEFAULT_ENABLE_OOP<br>
  <b>Recommended Default Value (Development Build):</b>true (HP-UX,
     Linux)<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>true (HP-UX,
     Linux)<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations: </b>In a dynamic, potentially multi-vendor,
     environment, the ability to run Providers in separate processes
     can significantly increase the stability, maintainability and
     supportability of the overall solution.&nbsp; Running Providers
     in separate process spaces: (1) helps isolate components (i.e.,
     cimserver and Providers) from a catastrophic failure
     (segmentation faults, memory leaks) of a single Provider and (2)
     reduces the risk of accidental or malicious sharing of sensitive
     data among Providers.&nbsp; This benefit comes at a cost.&nbsp;
     Moving Providers out of the cimserver process increases
     communication costs and can significantly increase response
     time.&nbsp; Actual results will vary, but it is common for
     response times to increase by a factor of 2.<br>
    <b>Note 1: </b>When forceProviderProcesses is true, the CIM
       Server will load each Provider Module (i.e., library) into a
       separate process. Providers in different Provider Modules
       cannot depend on a communication mechanism that
       requires them to run in the same process space.<br>
    <b>Note 2: </b>Although the catastrophic failure of an
       Out-Of-Process (OOP) Provider Module  will not result in a
       failure of the CIM Server process, if the failed OOP Provider
       Module included Indication Providers, Indications may be
       lost.&nbsp; If logging is enabled, the CIM Server will log a
       message informing administrators of what happened and what
       corrective actions can be taken.<br>
       <br>
       <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
         <tbody><tr>
           <th bgcolor="#cae6ca" width="168">Platform</th>
           <th bgcolor="#cae6ca" width="350">
             Source Configuration File</th>
         </tr>
         <tr align="center">
           <td width="168">Linux</td>
           <td align="left" width="350">
             Pegasus/Config/DefaultPropertyTableLinux.h</td>
         </tr>
         <tr align="center">
           <td width="168">HP-UX</td>
           <td align="left" width="350">
             Pegasus/Config/DefaultPropertyTableHpux.h</td>
         </tr>
         <tr align="center">
           <td width="168">OpenVMS</td>
           <td align="left" width="350">
             Pegasus/Config/DefaultPropertyTableVms.h</td>
         </tr>
         </tbody></table>
</ul>

<h5>home</h5>
<ul>
  <b>Description:&nbsp;</b>If set, this configuration option defines
     the runtime default value for PEGASUS_HOME.<br>
  <b>Default Value:&nbsp;</b>"./"<br>
  <b>Recommended Default Value (Development Build)</b>"./"<br>
  <b>Recommended Default Value (Release Build)""</b><br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<p>&nbsp;<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableVms.h</td>
       </tr>
       </tbody></table>
</p></ul>

<h5>hostname</h5>
<ul>
  <b>Description:&nbsp;</b> Can be used to override the local system supplied
      hostname without domain the CIM Server is using to build objects.
      If not set, querying this configuration option will report
      the system supplied hostname and behavior is not changed.<br>
      Setting this value to a valid hostname on CIM Server startup or as
      planned value will force the server to assume the configured name as the
      local hosts name. Setting this allows the administrator to set the name 
      that operations such as associator, reference etc. return with 
      object paths.<br>
      In common setups it is not recommended to explicitly set this value.
     <br>
  <b>Usage scenarios:&nbsp;</b> The following scenarios in which changing the
      default value makes sense are known today:<br>
          1. The case where what the CIM Server shall return to clients for
             host name is NOT the name of the current host but some 
             administrator defined name 
             (ex. system behind a firewall or some redirector).<br>
          2. Embedded systems that have a system set hostname which is not 
             valid and needs to be overridden by CIM administrator without 
             changing the actual IP configuration.
     <br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     blank<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     blank<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations: </b> When setting this configuration option the option 
      fullyQualifiedHostName should be adjusted too.<br>
      Providers returning the systems hostname in an 
      instance property might return a different value then the CIM server is 
      setting in the object path. hostnames explicitly set into the object 
      paths by providers will not be overridden by the CIM Server to allow 
      cross-namespace associations.
     <br>
      It is necessary to upgrade existing repositories using the repupgrade 
      utility when upgrading from an OpenPegasus version less than 2.12.
     <br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/DefaultPropertyOwner.cpp
</ul>

<h5>fullyQualifiedHostName</h5>
<ul>
  <b>Description:&nbsp;</b> Can be used to override the local system supplied
      fully qualified hostname (with domain) the CIM Server is using to build 
      objects.
      If not set, querying this configuration option will report
      the system supplied fully qualified hostname and behavior is 
      not changed.<br>
      Setting this value to a valid hostname on CIM Server startup or as
      planned value will force the server to assume the configured name as the
      local hosts name with domain. Setting this allows the administrator to 
      set the name that indication operations and the CIM_ObjectManager 
      assume for SystemName returned as instance and key properties.<br>
      In common setups it is not recommended to explicitly set this value.
     <br>
  <b>Usage scenarios:&nbsp;</b> The following scenarios in which changing the
      default value makes sense are known today:<br>
          1. The case where what the CIM Server shall return to clients for
             SystemName is NOT the name of the current host but some 
             administrator defined name
             (ex. system behind a firewall or some redirector).<br>
          2. Embedded systems that have a system set hostname which is not 
             valid and needs to be overridden by CIM administrator without 
             changing the actual IP configuration.
     <br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     blank<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     blank<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations: </b> When setting this configuration option the option 
      fullyQualifiedHostName should be adjusted too.<br>
      Providers returning the systems hostname in an 
      instance property might return a different value then the CIM server is 
      setting in SystemName.
     <br>
      It is necessary to upgrade existing repositories using the repupgrade 
      utility when upgrading from an OpenPegasus version less than 2.12.
     <br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/DefaultPropertyOwner.cpp
</ul>

<h5>httpPort</h5>
<ul>
  <b>Description:&nbsp;</b>OpenPegasus first attempts to look up the
     port number for HTTP using getservbyname for the 'wbem-http'
     service. The httpPort configuration setting is used only when the
     getservbyname lookup fails.<br>
  <b>Default Value:&nbsp;</b>blank<br>
  <b>Recommended Default Value (Development Build): </b>blank<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>5988<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>(1)The use of 5988 for WBEM HTTP is
     recommended by the DMTF.  This port has been registered with
     <a href="http://www.iana.org/assignments/port-numbers">
     IANA</a>. In a production environment, the recommendation is
     to use /etc/services to configure the value of this port. (2)
     With the release of OpenPegasus 2.5, the default values for
     httpPort was changed from 5988 to "". This
     change was made to allow the OpenPegasus to differentiate
     between a default setting of 5988 and a customer-defined
     setting of 5988.&nbsp; With this change,&nbsp; if the port
     number is explicitly set, the configured port will be used
     regardless of the settings in /etc/services. If no port number
     is specified, the server will continue to use the value in
     /etc/services.<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h5>httpsPort</h5>
<ul>
  <b>Description:&nbsp;</b>	
     OpenPegasus first attempts to look up the port number for HTTPS
     using getservbyname for the 'wbem-https' service. The httpsPort
     configuration setting is used only when the getservbyname lookup
     fails.<br>
  <b>Default Value:&nbsp;</b>blank<br>
  <b>Recommended Default Value (Development Build): </b>blank<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>5989<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>(1)The use of 5989 for WBEM HTTPS
     is recommended by the DMTF. This port has been registered with
     <a href="http://www.iana.org/assignments/port-numbers">IANA</a>.
     In a production environment, the recommendation is to use
     /etc/services to configure the value of this port.(2)
     With the release of OpenPegasus 2.5, the default values for
     httpPort was changed from 5989 to "". This
     change was made to allow the OpenPegasus to differentiate
     between a default setting of 5989 and a customer-defined
     setting of 5989.&nbsp; With this change,&nbsp; if the port number
     is explicitly set, the configured port will be used regardless
     of the settings in /etc/services. If no port number is specified,
     the server will continue to use the value in /etc/services.<br>
     <br>

     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h5>idleConnectionTimeout</h5>
<ul>
  <b>Description:&nbsp;</b>If set to a positive integer, this value
     specifies a minimum timeout value for idle client connections.
     If set to zero, idle client connections do not time out.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>0<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>0<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>A client connection is considered
     idle when it is not in the process of sending a request and
     the CIM Server is not processing a request from that connection.
     An idle connection timeout allows reclamation of the system
     resources allocated for idle CIM Server connections. Note that
     the CIM Server may allow an idle connection to persist longer
     than the configured timeout value based on server activity.
     Some client applications may not behave correctly if a
     connection timeout is introduced. Client compatibility should be
     considered when configuring an idle connection timeout value.
     The idle connection time is computed using the system clock.
     Thus, resetting the system clock may cause unexpected timeout
     behavior.This config property can be changed dynamically. The
     changes will apply to all new and existing connections. <br>
</ul>

<h5>maxFailedProviderModuleRestarts</h5>
<ul>
  <b>Description:&nbsp;</b>If set to a positive integer, this value
     specifies the number of times the failed provider module with
     indications enabled are restarted automatically before being
     moved to Degraded state. If set to zero, failed provider module
     is not restarted with indications enabled automatically and
     will be moved to Degraded state immediately.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>3<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>3<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>This option controls the automatic 
     re-enabling of the failed provider module with indications
     enabled. If the provider module with indications enabled fails
     very frequently, it affects the CIMServer normal operations because
     CIMServer would be busy with reloading the provider module every
     time it fails. This option would be helpful if the long running
     indication provider crashes and the management application want
     to receive the indications from the provider while provider fix
     is being delivered. In case of provider module grouping, if one of
     the indication provider crashes, it affects all indication providers
     in the provider modules of the group. Note that this is the facility
     provided by the CIMServer for temporary recovery of the provider and
     the ultimate goal SHALL be fixing the faulty provider.
</ul>

<h5>maxIndicationDeliveryRetryAttempts</h5>
<ul>
  <b>Description:&nbsp;</b> If set to a positive integer, value defines the number
         of times indication service will enable the reliableIndication feature and try
         to deliver an indication to a particular listener destination.
         This does not effect the original delivery attempt. A value of disables
         reliable indication feature completely, and cimserver will deliver the
         indication once.This is in accord with DTMF Specification 1054,
         Indication Profile, version 1.2.1.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>3<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>3<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b> This value is used to set the
     CIM_IndicationService.DeliveryRetryAttempts property. See
     CIM_IndicationService.DeliveryRetryAttempts property for more details. This
     option is supported only when PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT
     is defined.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/IndicationServicePropertyOwner.cpp<br>
</ul>

<h5>minIndicationDeliveryRetryInterval</h5>
<ul>
  <b>Description:&nbsp;</b> If set to a positive integer, this value defines
     the minimal time interval in seconds for the indication service to wait
     before retrying to deliver an indication to a listener destination that
     previously failed. Cimserver may take longer due to QoS or other processing.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>30<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>30<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b> This value is used to initialize the property
     CIM_IndicationService.DeliveryRetryInterval. See
     CIM_IndicationService.DeliveryRetryInterval property for more details. This
     option is supported only when PEGASUS_ENABLE_DMTF_INDICATION_PROFILE_SUPPORT
     is defined.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/IndicationServicePropertyOwner.cpp<br>
</ul>

<h5>listenAddress</h5>
<ul>
  <b>Description:&nbsp;</b> Network interface where the cimserver 
     should listen to for connections.For example listenAddress=All or
     listenAddress=121.12.33.112 or listenAddress=121.33.21.26,127.0.0.1,
     fe80::fe62:9346%eth0<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>All<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>No Specific suggestion<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Default value of "All" will make cimserver to listen on all the network interfaces.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/DefaultPropertyOwner.cpp<br>
</ul>

<h5>logdir</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the name of the directory
     to be used for the OpenPegasus specific log files.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>logs<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>$LOGDIR<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>This option is not supported if
     PEGASUS_USE_SYSLOGS is defined.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/LogPropertyOwner.cpp<br>
</ul>

<h5>logLevel</h5>
<ul>
  <b>Description:&nbsp;</b>Defines the desired level of logging.
     Valid values include: TRACE, INFORMATION, WARNING, SEVERE,
     FATAL.<br>
  <b>Default Value:&nbsp;</b>"INFORMATION"<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     "INFORMATION"<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>"SEVERE"<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b><br>
  <b>Source Configuration File:&nbsp;</b>
     Pegsus/Config/LogPropertyOwner.cpp<p>&nbsp;</p>
</ul>

<h5>mapToLocalName</h5>
<ul>
  <b>Description:&nbsp;</b> If 'true', all remote client names are translated
     to local ones using GSSAPI. This applies only to clients using Negotiate
     authentication method, i.e. when "httpAuthType" runtime variable is set to
     "negotiate".<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     false<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This option is available only when Pegasus is
     compiled with PEGASUS_NEGOTIATE_AUTHENTICATION=true.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp<p>&nbsp;</p>
</ul>

<h5>maxLogFileSizeKBytes</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the maximum size of the logfile in Kilo
     Bytes. If the logfile size exceeds maxLogFileSizeKBytes logfile will be pruned.<br>
  <b>Default Value:&nbsp;</b>32768<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b> 32768<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>32768<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):</b>&nbsp;No/No<br>
  <b>Dynamic?:</b>&nbsp;Yes<br>
  <b>Considerations:</b> This option is not supported if PEGASUS_USE_SYSLOGS is defined. Minimum accepted value is 32 KB.&nbsp;<br>
  <b>Source Configuration File:</b>&nbsp; Pegsus/Config/LogPropertyOwner.cpp<p>&nbsp;</p>
</ul>
<h5>maxProviderProcesses</h5>
<ul>
  <b>Description:</b>&nbsp;Limits the number of provider
     processes (see 'forceProviderProcesses) that may run
     concurrently. A 'maxProviderProcesses' value of '0' indicates
     that the number of Provider Agent processes is unlimited<br>
  <b>Default Value:&nbsp;</b>0<br>
  <b>Recommended Default Value (Development Build):</b>&nbsp;0<br>
  <b>Recommended Default Value (Release Build):</b>&nbsp;0<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/Yes<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>Consider there are five provider processes
     already running and the maxProviderProcesses is dynamically changed to
     four. In this case though new provider processes will not be created
     but existing five will continue running<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">
           Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/DefaultPropertyTableVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h5>messageDir</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the name of the directory to
     be used for the OpenPegasus translated messages.<br>
  <b>Default Value:&nbsp;</b>msg<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>msg<br>
  <b>Recommended Default Value (Release Build):</b>
     $MESSAGEDIR/msg<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Only used when message localization
     is enabled. &nbsp;See PEGASUS_HAS_MESSAGES for details.<br>
  <b>Source Configuration File:&nbsp;</b>
     FileSystemPropertyOwner.cpp<br>
</ul>

<h5>providerDir</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the names of the directories
     that contains Provider executables.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>lib<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $PROVIDERDIRS<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>The CIM Server runs as a privileged
     user. And, since Providers run in the same process space as the
     CIM Server, Providers also have privileged access to the
     system. Allowing a registered Provider&#8217;s executable to be
     replaced with malicious code would result in a critical
     security defect, giving a malicious user privileged access
     to the system. Administrators are responsible for ensuring
     that only trusted Providers are loaded into providerDir.
     In order to simplify the management task associated with
     securing Provider executable, the value of providerDir can be
     fixed at build time (i.e., set to one or more fixed, well-known
     locations).<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/FileSystemPropertyOwner.cpp<br>
</ul>

<h5>providerManagerDir</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the name of the directory that
     contains the ProviderManager plugin libraries.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>lib<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $PROVIDERMANAGERDIRS<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Should be a dedicated directory to
     minimize inspection of non-applicable files. Additionally,
     since all calls to the providers go through the provider
     managers, the same care should be taken with regards to
     security for the provider manager directory, as for provider
     directories.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/FileSystemPropertyOwner.cpp<br>
</ul>

<h5>repositoryDir</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the name of the directory
     to be used for the OpenPegasus repository.<br>
  <b>Recommended Default Value (Development Build): </b>repository<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $REPOSITORYDIR/repository<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b><br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/FileSystemPropertyOwner.cpp<p><br>
</p></ul>

<h5>repositoryIsDefaultInstanceProvider</h5>
<ul>
  <b>Description:&nbsp;</b>If true, the Repository functions
     as the Instance Provider for all classes for which there
     is not an explicitly registered Provider.  This flag is
     also used to control the behavior of the repository when
     processing association operators.<br>
  <b>Recommended Default Value (Development Build): </b>true<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/Yes<br>
  <b>Dynamic?: &nbsp;</b>No<br>
  <b>Considerations: &nbsp;</b>This flag can be used to configure
     the CIM Server to allow the Repository to be used by CIM Clients
     and CIM Providers as a dynamic data store. The setting of this
     flag will significantly affect CIM Server behavior as viewed
     by the CIM Client.<br>

     The following issues should be considered when setting
     repositoryIsDefaultInstanceProvider=true:

     <ul>
       <li><b>Authorization.</b> &nbsp;The repository has no
           concept of which users (or components) are authorized to
           perform which operations.</li>
       <li><b>Appearance of instrumentation.</b> &nbsp;A client application
           cannot determine whether instrumentation exists for a
           given CIM class. For example,&nbsp; imagine a client
           issues a CreateInstance operation on a Disk class
           for&nbsp;&nbsp;&nbsp; which no provider is registered.
           &nbsp;The instance will be stored in the repository, and
           the client gets a "success" response. Does that mean&nbsp;a
           disk device has been created on the server? Even worse,
           when another client issues an EnumerateInstances
           operation,&nbsp;the spurious Disk instance is returned.
           &nbsp;With repositoryIsDefaultInstanceProvider=false, the
           CreateInstance operation above would have returned a
           NOT_SUPPORTED error.</li>
       <li><b>Potential for inconsistent data.</b> &nbsp;Using the
           repository as a data cache increases the probability
           that a client will see stale or incorrect data.  A
           provider can better control the correlation
           between the data returned and the current state of the
           underlying managed resource (whether or not the provider
           caches the data).</li>
     </ul>
     <br>

     The following issues should be considered when setting
     repositoryIsDefaultInstanceProvider=false:

     <ul>
       <li><b>Provider Availability.</b> Certain Providers have been
           developed to use the Repository as a dynamic data store.
           These Providers are currently not supported on system
           where this flag is disabled. E.g., the Common Diagnostics
           Model (CDM) Provider
           (http://developer.intel.com/design/servers/cdm/)
           relies on use of the Repository to store instances
           of CIM_DiagnosticSetting.&nbsp; If this flag set to
           false, this Provider will not function correctly. Note
           that this feature is supported by other WBEM
           implementation.&nbsp; Therefore, disabling this feature
           can increase the cost of migrating existing Providers to
           OpenPegasus.</li>
      </ul>

  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/RepositoryPropertyOwner.cpp<br>
</ul>

<h5>shutdownTimeout</h5>
<ul>
  <b>Description:&nbsp;</b>When a cimserver -s shutdown command is
     issued, specifies the maximum time in seconds for the CIM Server
     to complete outstanding CIM operation requests before shutting
     down; if the specified timeout period expires, the CIM Server
     will shut down, even if there are still CIM operations in
     progress. Minimum value is 2 seconds.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>10<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>10<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b><br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/ShutdownPropertyOwner.cpp<br>
</ul>

<h5>slp</h5>
<ul>
  <b>Description:&nbsp;</b>When set to true, OpenPegasus activates
     an SLP SA and issues DMTF defined SLP advertisements to this SA
     on startup.<br>
  <b>Default Value:&nbsp;</b>false<br>
  <b>Recommended Default Value (Development Build): </b>false<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<p>&nbsp;<br>
  <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" height="80" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" height="16" width="168">Platform</th>
         <th bgcolor="#cae6ca" height="16" width="350">
           Source Configuration File</th>
       </tr>
       <tr align="center">
        <td height="14" width="168">Linux</td>
         <td align="left" height="14" width="350">
           Pegasus/Config/DefaultPropertyTableLinux.h</td>
       </tr>
       <tr align="center">
         <td height="14" width="168">HP-UX</td>
         <td align="left" height="14" width="350">
           Pegasus/Config/DefaultPropertyTableHpux.h</td>
       </tr>
       <tr align="center">
         <td height="16" width="168">OpenVMS</td>
         <td align="left" height="16" width="350">
           Pegasus/Config/DefaultPropertyTableVms.h</td>
       </tr>
       </tbody></table>
</p></ul>

<h5>slpProviderStartupTimeout</h5>
<ul>
  <b>Description:&nbsp;</b>Timeout value in milli seconds used to specify 
    how long the registration with an SLP SA may take. Registration will be 
    retried three times. This value only needs to be increased in case that 
    the loading of a set of providers who reporting their implementation of a 
    registered profile takes very long.<br>
  <b>Default Value:&nbsp;</b>300000<br>
  <b>Recommended Default Value (Development Build): </b>300000<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>300000<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<p>&nbsp;<br>
  <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" height="80" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" height="16" width="168">Platform</th>
         <th bgcolor="#cae6ca" height="16" width="350">
           Source Configuration File</th>
       </tr>
       <tr align="center">
        <td height="14" width="168">Linux</td>
         <td align="left" height="14" width="350">
           Pegasus/Config/DefaultPropertyTable.h</td>
       </tr>
       <tr align="center">
         <td height="14" width="168">HP-UX</td>
         <td align="left" height="14" width="350">
           Pegasus/Config/DefaultPropertyTable.h</td>
       </tr>
       <tr align="center">
         <td height="16" width="168">OpenVMS</td>
         <td align="left" height="16" width="350">
           Pegasus/Config/DefaultPropertyTable.h</td>
       </tr>
       </tbody></table>
</p></ul>

<h5>socketWriteTimeout</h5>
<ul>
  <b>Description:&nbsp;</b>If the CIM Server receives an
     EWOULDBLOCK/EAGAIN error on a non-blocking write,
     socketWriteTimeout defines the number of seconds the
     CIM Server will wait for the socket to get ready and resume
     writing data.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     20 (seconds)<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     20 (seconds)<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Considerations:&nbsp;</b>Any changes made to this config property
     dynamically will apply to new CIM Server connections only
     keeping old already established connections unchanged.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/DefaultPropertyTable.h
</ul>

<h5>sslCertificateFilePath</h5>
<ul>
  <b>Description:&nbsp;</b>Contains the CIM Server SSL
     Certificate.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     server.pem<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $CERTIFICATEDIR/server.pem"<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations: </b>For a more detailed look at SSL options
     and their ramifications, please see the SSL guidelines.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp
</ul>

<h5>sslCipherSuite</h5>
<ul>
  <b>Description:&nbsp;</b>String containing OpenSSL cipher
     specifications to configure the cipher suite the client is
     permitted to negotiate with the server during the SSL
     handshake phase.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     DEFAULT (the default cipher list of OpenSSL)<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     DEFAULT (the default cipher list of OpenSSL)<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>The value should be mentioned between
     single quotes since it can contain special characters like .+,
     !, -.. For more details look at SSL ciphers.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp
</ul>

<h5>sslBackwardCompatibility</h5>
<ul>
  <b>Description:&nbsp;</b> If set to true, OpenPegasus support
     SSLv3 and TLSv1 protocol.If set to false OpenPegasus support
     only TLS1.2 protocol for openssl 1.0.1+ <br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     false<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     false<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b> For a more detailed look at SSL options
     and their ramifications, please see the SSL guidelines.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp
</ul>

<h5>sslClientVerificationMode</h5>
<ul>
  <b>Description:&nbsp;</b>Describes the desired level of support
     for certificate-based authentication.
    <ul style="margin-top: 0in;" type="circle">
      <li>&#8220;<b>required</b>&#8221; &#8211; The server requires certificate-based
          client authentication.&nbsp; A client MUST present a
          trusted certificate in order to access the CIM Server.&nbsp;
          If the client fails to send a certificate or sends an
          untrusted certificate, the connection will be rejected.</li>
      <li>&#8220;<b>optional</b>&#8221; &#8211; The server supports, but does not
          require, certificate-based client authentication. The
          server will request and attempt to validate a client
          certificate, however the connection will be accepted even
          if no certificate is sent or an untrusted certificate is
          sent.&nbsp; The server will then seek to authenticate the
          client via an authentication header.</li>
      <li>&#8220;<b>disabled</b>&#8221; &#8211; The server does not support
          certificate-based client authentication.</li>
    </ul>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     disabled<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     disabled<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>(1) This property is only used if
     <b>enableHttpsConnection</b> is  <b>"true"</b>.
     (2) If the platform does not support PEGASUS_LOCAL_DOMAIN_SOCKET,
     OpenPegasus attempts to use either HTTPS or
     HTTP to establish a local connection (connectLocal).&nbsp;
     For platforms that do not support PEGASUS_LOCAL_DOMAIN_SOCKET,
     Clients which use connectLocal, such as cimconfig -l -c,
     cimprovider -l -s and cimserver -s, will not work if&nbsp; the
     "sslClientVerificationMode" variable is set to
     "required" and HTTP is disabled.&nbsp; For these
     platforms, the recommended course of action is to change the
     property value to "optional."<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp
</ul>
	
<h5>sslKeyFilePath</h5>
<ul>
  <b>Description:&nbsp;</b>Contains the private key for the CIM
     Server SSL Certificate.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     file.pem<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $CERTIFICATEDIR/file.pem<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations: </b>File should be readable only by the
     user the cimserver is running as and/or privileged users. The
     file should be writeable only by a privileged user.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/SecurityPropertyOwner.cpp<br>
</ul>

<h5>sslTrustStore</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the OpenSSL
     truststore. Consistent with the OpenSSL implementation, a
     truststore can be either a file or directory. If the truststore
     is a directory, all the certificates within the directory are
     considered trusted.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     client.pem<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $CERTIFICATEDIR/client.pem<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>Yes<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegsus/Config/SecurityPropertyOwner.cpp
</ul>

<h5>sslTrustStoreUserName</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the system user name to be
     associated with all certificate-based authenticated requests.<br>
  <b>Recommended Default Value (Development Build): </b>NONE<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>NONE<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>This property has no default; for
     security reasons, the system administrator must explicitly
     specify this value.&nbsp; This feature allows a single user
     name to be specified.&nbsp; This user will be associated
     with all certificates in the truststore.&nbsp; In the future,
     OpenPegasus will allow a system administrator to associate a
     distinct user name with each certificate.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegsus/Config/SecurityPropertyOwner.cpp<br>
</ul>

<h5>traceComponents</h5>
<ul>
  <b>Description:&nbsp;</b>Defines the components to be traced.<br>
  <b>Default Value:&nbsp;</b>""<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>""<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>""<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</b>No/Yes<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/TracePropertyOwner.cpp<br>
</ul>

<h5>traceFacility</h5>
<ul>
  <b>Description:&nbsp;</b>Defines the desired facility for trace
     messages. Valid values include: "File"
     , "Log" and "Memory" .<br>
  <b>Default Value:&nbsp;</b>File<br>
  <b>Recommended Default Value (Development Build): </b>File<br>
  <b>Recommended Default Value (Release Build): </b>File<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/Yes<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Case Sensitive?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>If you specify "File",
     trace messagesare written into the file specified by the
     configuration option traceFilePath. If you specify
     "Log", trace messages are written to the
     OpenPegasus Log. If you specify Memory, the trace messages 
     are collected in a wrap-around memory buffer. 
     If this memory is part of a dump the trace messages can be 
     found by the eye-catcher "PEGASUSMEMTRACE" at 
     the top of the memory buffer. The trace is in clear text and 
     the last written message has the suffix "EOTRACE".<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/TracePropertyOwner.cpp<br>
</ul>

<h5>traceFilePath</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the location of the
     OpenPegasus trace file.<br>
  <b>Default Value:&nbsp;</b>cimserver.trc<br>
  <b>Recommended Default Value (Development Build):</b>
     cimserver.trc<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $TRACEDIR/cimserver.trc<br>
  <b>Recommend To Be Fixed/Hidden (Development Build):</b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build): </b>Yes<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/TracePropertyOwner.cpp<br>
</ul>

<h5>traceLevel</h5>
<ul>
  <b>Description:&nbsp;</b>Defines the desired level of
     tracing. Valid values include: 0, 1, 2, 3, 4, 5.<br>
  <b>Default Value:&nbsp;</b>0<br>
  <b>Recommended Default Value (Development Build): </b>0<br>
  <b>Recommended Default Value (Release Build): </b>0&lt;<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/Yes<br>
  <b>Dynamic?:&nbsp;</b>Yes<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/TracePropertyOwner.cpp<br>
</ul>

<h5>traceMemoryBufferKbytes</h5>
<ul>
  <b>Description:&nbsp;</b>Defines the size of the buffer for 
    in memory tracing in kbytes ( 2<sup>10</sup> bytes ). 
    Smallest value is 16.<br>
  <b>Default Value:&nbsp;</b>10240<br>
  <b>Recommended Default Value (Development Build): </b>10240<br>
  <b>Recommended Default Value (Release Build): </b>10240<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/No<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Case Sensitive?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Is ignored if configuration 
    property traceFacility is not set to Memory.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Config/TracePropertyOwner.cpp<br>
</ul>

<h5>traceFileSizeKBytes</h5>
<ul>
  <b>Description:&nbsp;</b>Defines the size of the tracefile in Kilo bytes. The trace file will be
     rolled once its size exceeds the specified size. <br>
  <b>Default Value:&nbsp;</b>1048576<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>1048576<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>1048576<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):</b>&nbsp;No/Yes<br>
  <b>Dynamic?:</b>&nbsp;Yes<br>
  <b>Considerations:</b>Minimum accepted value is 10240 KB,Maximum accepted value is 2097152 KB. &nbsp;<br>
  <b>Source Configuration File:</b>&nbsp; Pegsus/Config/TracePropertyOwner.cpp<p>&nbsp;</p>
</ul>

<h5>numberOfTraceFiles</h5>
<ul>
  <b>Description:&nbsp;</b>Specifies the number of the tracefiles for rolling.<br>
  <b>Default Value:&nbsp;</b>3<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>3<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>3<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):</b>&nbsp;No/Yes<br>
  <b>Dynamic?:</b>&nbsp;Yes<br>
  <b>Considerations:</b>Minimum accepted value is 3,Maximum accepted value is 20. &nbsp;<br>
  <b>Source Configuration File:</b>&nbsp; Pegsus/Config/TracePropertyOwner.cpp<p>&nbsp;</p>
</ul>

<h5>webRoot</h5>
<ul>
  <b>Description:&nbsp;</b> Points to a location where the static web pages to
  be served by the pegasus webserver are stored.<br>
  <b>Default Value:&nbsp;</b>www<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>www<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>$WEBCONFDIR/www<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):</b>&nbsp;Yes/Yes<br>
  <b>Dynamic?:</b>&nbsp;No<br>
  <b>Considerations:</b> When not fixed and hidden, it can be modified to
  point to a location having spurious pages. Please consider fixing this value. &nbsp;<br>
  <b>Source Configuration File:</b>&nbsp; Pegsus/Config/DefaultPropertyOwner.cpp<p>&nbsp;</p>
</ul>

<h5>indexFile</h5>
<ul>
  <b>Description:&nbsp;</b> Specifies the name of index file used by pegasus webserver,
  default to index.html. This file should be available at the webRoot path.<br>
  <b>Default Value:&nbsp;</b>index.html<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>index.html<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>index.html<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):</b>&nbsp;Yes/Yes<br>
  <b>Dynamic?:</b>&nbsp;No<br>
  <b>Considerations:</b> &nbsp; Hide it and fixed in release build to prevent
  using any file as index file<br>
  <b>Source Configuration File:</b>&nbsp; Pegsus/Config/DefaultPropertyOwner.cpp<p>&nbsp;</p>
</ul>

<h5>mimeTypesFile</h5>
<ul>
  <b>Description:&nbsp;</b> Refers to the file which holds the mime types being
  served by the pegasus webserver.<br>
  <b>Default Value:&nbsp;</b>www/mimeTypes.txt<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>www/mimeTypes.txt<br>
  <b>Recommended Default Value (Release
      Build):&nbsp;</b>$WEBCONFDIR/www/mimeTypes.txt<br>
  <b>Recommend To Be Fixed/Hidden (Development Build): </b>No/No<br>
  <b>Recommend To Be Fixed/Hidden (Release Build):</b>&nbsp;Yes/Yes<br>
  <b>Dynamic?:</b>&nbsp;No<br>
  <b>Considerations:</b>&nbsp;Fix and make it read only when to prevent
  modification in deployment<br>
  <b>Source Configuration File:</b>&nbsp; Pegsus/Config/DefaultPropertyOwner.cpp<p>&nbsp;</p>
</ul>


<h3>Configuration Constants</h3>

<h4>Definitions</h4>

<h5>static char CURRENT_CONFIG_FILE [] = </h5>
<ul>
  <b>Description:&nbsp;</b>Default file name for the current
     configuration file.<br>
  <b>Recommended Default Value (Development Build):</b>
     cimserver_current.conf<br>
  <b>Recommended Default Value (Release Build): </b>
     $CONFIGDIR/cimserver_current.conf<br>
  <b>Dynamic?:&nbsp;</b>No&nbsp;<br>
  <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">
           Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/ConfigFileDirLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">ConfigFileDirHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/ConfigFileDirVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h5>static char PLANNED_CONFIG_FILE [] = </h5>
<ul>
  <b>Description:&nbsp;</b>Default file name for the planned
     configuration file.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     cimserver_planned.conf<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $CONFIGDIR/cimserver_planned.conf<br>
  <b>Dynamic?:&nbsp;</b>No<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">
           Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/ConfigFileDirLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
           Pegasus/Config/ConfigFileDirHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/ConfigFileDirVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h5>static char CIMSERVER_START_FILE [] = </h5>
<ul>
  <b>Description:&nbsp;</b>This is for the default file name
     for the cimserver startup file containing the PID.<br>
  <b>Default Value:&nbsp;</b>/tmp/cimserver_start.conf<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     /tmp/cimserver_start.conf<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $PIDFILE<br>
  <b>Dynamic?:&nbsp;</b>No<br>
     <br>
     <table bordercolordark="#666666" bordercolorlight="#CCCCCC" style="font-family: Arial;" border="1" cellspacing="1" width="531">
       <tbody><tr>
         <th bgcolor="#cae6ca" width="168">Platform</th>
         <th bgcolor="#cae6ca" width="350">
           Source Configuration File</th>
       </tr>
       <tr align="center">
         <td width="168">Linux</td>
         <td align="left" width="350">
           Pegasus/Config/ConfigFileDirLinux.h</td>
       </tr>
       <tr align="center">
         <td width="168">HP-UX</td>
         <td align="left" width="350">
           Pegasus/Config/ConfigFileDirHpux.h</td>
       </tr>
       <tr align="center">
         <td width="168">OpenVMS</td>
         <td align="left" width="350">
           Pegasus/Config/ConfigFileDirVms.h</td>
       </tr>
       </tbody></table>
</ul>

<h3>Configuration Macros</h3>

<h4>Definitions</h4>

<h5>PEGASUS_SSLCLIENT_CERTIFICATEFILE</h5>
<ul>
  <b>Description:&nbsp;</b><br>
  <b>Recommended Default Value (Development Build): </b>client.pem<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $CERTIFICATEDIR/client.pem<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Common/Constants.h<br>
</ul>

<h5>PEGASUS_SSLCLIENT_RANDOMFILE</h5>
<ul>
  <b>Description:&nbsp;</b>On platforms that do not support
     /dev/random or /dev/urandom, OpenSSL will use this file to
     seed the PRNG (Pseudo-Random Number Generator). This
     PEGASUS_SSLCLIENT_RANDOMFILE defines the default CIM
     Client random file.<br>
  <b>Recommended Default Value (Development Build):</b>ssl.rnd<br>
  <b>Recommended Default Value (Release Build):</b>
     $RANDOMDIR/ssl.rnd<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>Use of this variable requires&nbsp;
     PEGASUS_HAS_SSL to be set.&nbsp; CIM Client use of a
     shared random file is not recommended.&nbsp; On systems where
     /dev/random or /dev/urandom are not available, CIM Clients are
     encouraged to generate a unique random file which
     contains sufficient entropy.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Common/Constants.h<br>
</ul>

<h5>PEGASUS_SSLSERVER_RANDOMFILE</h5>
<ul>
  <b>Description:&nbsp;</b>On platforms that do not support
     /dev/random or /dev/urandom, OpenSSL will use this file
     to seed the PRNG (Pseudo-Random Number Generator). This
     PEGASUS_SSLSERVER_RANDOMFILE defines the CIM Server
    random file.<br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     cimserver.rnd<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
    $RANDOMDIR/cimserver.rnd<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Considerations:&nbsp;</b>1)Use of this variable
     requires&nbsp; PEGASUS_HAS_SSL to be set.(2) On systems where
     /dev/random or /dev/urandom are not available, CIM Server
     vendors need to be sure that the cimserver.rnd file
     contains sufficient entropy and is uniquely generated for
     each system.<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Common/Constants.h<b><br>
</b></ul>

<h5><b>PEGASUS_LOCAL_AUTH_DIR</b></h5>
<ul>
<b>  <b>Description:</b>&nbsp;</b>For local connections (i.e.,
     connectLocal), OpenPegasus uses a file-based authentication
     mechanism.<br>
  <b>Recommended Default Value (Development Build): </b>/tmp<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $LOCALAUTHDIR/localauth<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Common/Constants.h<br>
</ul>

<h5>PEGASUS_LOCAL_DOMAIN_SOCKET_PATH</h5>
<ul>
  <b>Description:&nbsp;</b><br>
  <b>Recommended Default Value (Development Build):&nbsp;</b>
     /tmp/cimxml.socket<br>
  <b>Recommended Default Value (Release Build):&nbsp;</b>
     $SOCKETDIR/cimxml.socket<br>
  <b>Dynamic?:&nbsp;</b>No<br>
  <b>Source Configuration File:&nbsp;</b>
     Pegasus/Common/Constants.h<br>
</ul>

<hr>
<p>Licensed to The Open Group (TOG) under one or more contributor license
agreements.  Refer to the OpenPegasusNOTICE.txt file distributed with
this work for additional information regarding copyright ownership.
Each contributor licenses this file to you under the OpenPegasus Open
Source License; you may not use this file except in compliance with the
License.</p>
<p>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:</p>
<p>The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.</p>
<p>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.</p>
<hr>
</body></html>

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2