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

Diff for /pegasus/doc/BuildAndReleaseOptions.html between version 1.11 and 1.23

version 1.11, 2008/11/26 08:15:30 version 1.23, 2011/01/07 11:26:05
Line 518 
Line 518 
      platforms.<br>      platforms.<br>
 </ul> </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> <h5>PEGASUS_EMANATE_INCLUDE_DIR</h5>
 <ul> <ul>
   <b>Description:&nbsp;</b>Specifies the location of the EMANATE   <b>Description:&nbsp;</b>Specifies the location of the EMANATE
Line 1610 
Line 1627 
      Handler to be supported.<br>      Handler to be supported.<br>
 </ul> </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>
   </ul>
   
   
 <h5>PEGASUS_USE_OPENSLP</h5> <h5>PEGASUS_USE_OPENSLP</h5>
 <ul> <ul>
   <b>Description:&nbsp;</b>OpenSLP, <a href="http://www.openslp.org">   <b>Description:&nbsp;</b>OpenSLP, <a href="http://www.openslp.org">
Line 1653 
Line 1685 
      the "Release Build" configuration options. By default,      the "Release Build" configuration options. By default,
      OpenPegasus is built using the &quot;Development Build"      OpenPegasus is built using the &quot;Development Build"
      configuration options.<br>      configuration options.<br>
   <b>Default Value:&nbsp;</b>Not Set<br>    <b>Default Value:&nbsp;</b>false<br>
   <b>Recommended Value (Development Build):&nbsp;</b>Not Set<br>    <b>Recommended Value (Development Build):&nbsp;</b>false<br>
   <b>Recommended Value (Release Build):&nbsp;</b>Set<br>    <b>Recommended Value (Release Build):&nbsp;</b>true<br>
   <b>Required:&nbsp;</b>No<br>   <b>Required:&nbsp;</b>No<br>
   <b>Considerations:&nbsp;</b>(1)The   <b>Considerations:&nbsp;</b>(1)The
      PEGASUS_USE_RELEASE_CONFIG_OPTIONS variable allows a platform      PEGASUS_USE_RELEASE_CONFIG_OPTIONS variable allows a platform
Line 1690 
Line 1722 
      titled "Configuration Properties" for additional detail.<br>      titled "Configuration Properties" for additional detail.<br>
 </ul> </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> <h5>PEGASUS_USE_SQLITE_REPOSITORY</h5>
 <ul> <ul>
   <b>Description:&nbsp;</b>If true, new repository stores are created   <b>Description:&nbsp;</b>If true, new repository stores are created
Line 1774 
Line 1846 
   export PEGASUS_HOME=/home/pegasusbld/pegasus/build<br>   export PEGASUS_HOME=/home/pegasusbld/pegasus/build<br>
   export PEGASUS_PLATFORM=LINUX_IX86_GNU<br>   export PEGASUS_PLATFORM=LINUX_IX86_GNU<br>
   #export PEGASUS_PLATFORM=LINUX_IA64_GNU<br>   #export PEGASUS_PLATFORM=LINUX_IA64_GNU<br>
   export PEGASUS_DISABLE_CQL=true <br>    export PEGASUS_ENABLE_CQL=false<br>
   export PEGASUS_PAM_AUTHENTICATION=true <br>   export PEGASUS_PAM_AUTHENTICATION=true <br>
   export PEGASUS_USE_PAM_STANDALONE_PROC=true<br>   export PEGASUS_USE_PAM_STANDALONE_PROC=true<br>
   export PEGASUS_HAS_SSL=yes<br>   export PEGASUS_HAS_SSL=yes<br>
Line 2170 
Line 2242 
   <b>Recommended Default Value (Release 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 (Development Build): </b>No/No<br>
   <b>Recommend To Be Fixed/Hidden (Release Build):&nbsp;</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>    <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>   <br>
      <table border="1" cellspacing="1" bordercolordark="#666666"      <table border="1" cellspacing="1" bordercolordark="#666666"
          bordercolorlight="#CCCCCC" width=531          bordercolorlight="#CCCCCC" width=531
Line 2274 
Line 2370 
      Pegasus/Config/SecurityPropertyOwner.cpp<p>&nbsp;</p>      Pegasus/Config/SecurityPropertyOwner.cpp<p>&nbsp;</p>
 </ul> </ul>
  
 <h5>enableSSLExportClientVerification</h5>  
 <ul>  
   <b>Description:&nbsp;</b>If true, the CIM Server allows HTTPS  
      connection for CIMExport requests on the port specified by the  
      service name &quot;wbem-exp-https&quot;.<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>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>Source Configuration File:&nbsp;</b>  
      Pegasus/Config/SecurityPropertyOwner.cpp</p>  
 </ul>  
   
   
 <h5>enableSubscriptionsForNonprivilegedUsers</h5> <h5>enableSubscriptionsForNonprivilegedUsers</h5>
 <ul> <ul>
   <b>Description:&nbsp;</b>If true, operations (create instance,   <b>Description:&nbsp;</b>If true, operations (create instance,
Line 2333 
Line 2413 
      Pegasus/Config/NormalizationPropertyOwner.cpp      Pegasus/Config/NormalizationPropertyOwner.cpp
 </ul> </ul>
  
   
 <h5><b>exportSSLTrustStore</b></h5>  
 <ul>  
   <b>Description:&nbsp;</b>Specifies the location of the OpenSSL  
      truststore for Indications. 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>Default Value:&nbsp;</b>indication_trust.pem<br>  
   <b>Recommended Default Value (Development Build):&nbsp;</b>  
      indication_trust.pem<br>  
   <b>Recommended Default Value (Release Build):&nbsp;</b>  
      $CERTIFICATEDIR/indication_trust.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>  
      Pegasus/Config/SecurityPropertyOwner.cpp</p>  
 </ul>  
   
 <h5>forceProviderProcesses</h5> <h5>forceProviderProcesses</h5>
 <ul> <ul>
   <b>Description:&nbsp;</b>If true, the CIM Server runs Providers   <b>Description:&nbsp;</b>If true, the CIM Server runs Providers
Line 2586 
Line 2646 
      changes will apply to all new and existing connections. <br>      changes will apply to all new and existing connections. <br>
 </ul> </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>logdir</h5> <h5>logdir</h5>
 <ul> <ul>
   <b>Description:&nbsp;</b>Specifies the name of the directory   <b>Description:&nbsp;</b>Specifies the name of the directory
Line 3033 
Line 3121 
 <ul> <ul>
   <b>Description:&nbsp;</b>Defines the desired facility for trace   <b>Description:&nbsp;</b>Defines the desired facility for trace
      messages. Valid values include: &quot;File&quot;      messages. Valid values include: &quot;File&quot;
      and &quot;Log&quot;.<br>       , &quot;Log&quot; and &quot;Memory&quot; .<br>
   <b>Default Value:&nbsp;</b>File<br>   <b>Default Value:&nbsp;</b>File<br>
   <b>Recommended Default Value (Development Build): </b>File<br>   <b>Recommended Default Value (Development Build): </b>File<br>
   <b>Recommended Default Value (Release Build): </b>File<br>   <b>Recommended Default Value (Release Build): </b>File<br>
Line 3045 
Line 3133 
      trace messagesare written into the file specified by the      trace messagesare written into the file specified by the
      configuration option traceFilePath. If you specify      configuration option traceFilePath. If you specify
      &quot;Log&quot;, trace messages are written to the      &quot;Log&quot;, trace messages are written to the
      OpenPegasus Log.<br>       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 &quot;PEGASUSMEMTRACE&quot; at
        the top of the memory buffer. The trace is in clear text and
        the last written message has the suffix &quot;EOTRACE&quot;.<br>
   <b>Source Configuration File:&nbsp;</b>   <b>Source Configuration File:&nbsp;</b>
      Pegasus/Config/TracePropertyOwner.cpp<br>      Pegasus/Config/TracePropertyOwner.cpp<br>
 </ul> </ul>
Line 3080 
Line 3173 
      Pegasus/Config/TracePropertyOwner.cpp<br>      Pegasus/Config/TracePropertyOwner.cpp<br>
 </ul> </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>
   
 <h3>Configuration Constants</h3> <h3>Configuration Constants</h3>
  
 <h4>Definitions</h4> <h4>Definitions</h4>
Line 3276 
Line 3387 
 </ul> </ul>
  
 <hr> <hr>
 <p><font size="2">  <p>Licensed to The Open Group (TOG) under one or more contributor license
 Copyright (c) 2004 EMC Corporation; Hewlett-Packard  Development  agreements.  Refer to the OpenPegasusNOTICE.txt file distributed with
 Company, L.P.; IBM Corp.; The Open Group; VERITAS Software Corporation<br>  this work for additional information regarding copyright ownership.
 Copyright (c) 2006 Hewlett-Packard Development Company, L.P.; IBM Corp.;  Each contributor licenses this file to you under the OpenPegasus Open
 EMC Corporation; Symantec Corporation; The Open Group.<br>  Source License; you may not use this file except in compliance with the
 <br>  License.</p>
 Permission is hereby granted, free of charge, to any person  <p>Permission is hereby granted, free of charge, to any person obtaining a
 obtaining a copy&nbsp; of this software and associated documentation files  copy of this software and associated documentation files (the "Software"),
 (the &quot;Software&quot;), to deal in the Software without restriction,  to deal in the Software without restriction, including without limitation
 including without limitation the rights to use, copy,  the rights to use, copy, modify, merge, publish, distribute, sublicense,
 modify, merge, publish, distribute, sublicense, and/or sell copies  and/or sell copies of the Software, and to permit persons to whom the
 of the Software, and to permit persons to whom the Software is  Software is furnished to do so, subject to the following conditions:</p>
 furnished to do so, subject to the following conditions:  <p>The above copyright notice and this permission notice shall be included
 <br><br>  in all copies or substantial portions of the Software.</p>
 THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED  <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
 IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE  OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
 SOFTWARE IS PROVIDED&nbsp; &quot;AS IS&quot;, WITHOUT WARRANTY OF ANY  MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
 KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
 OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND  CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
 NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS  TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
 BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN  SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
 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.  
 </font></p>  
   
 <hr> <hr>
 <p>Template last modified: January 20th 2004 by Martin Kirk<br>Template version: 1.6</p>  
   
 </body> </body>
 </html> </html>


Legend:
Removed from v.1.11  
changed lines
  Added in v.1.23

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2