|
version 1.8, 2008/11/12 17:22:30
|
version 1.11, 2008/11/26 08:15:30
|
|
|
|
| to false), a build error will be generated. | to false), a build error will be generated. |
| </ul> | </ul> |
| | |
| <h5>PEGASUS_ENABLE_ENCAPSULATED_XML</h5> |
|
| <ul> |
|
| <b>Description: </b> |
|
| This option enables the "encapsulated XML" feature. It is used in |
|
| conjunction with the "internal binary protocol" feature (see |
|
| PEGASUS_ENABLE_INTERNAL_BINARY_PROTOCOL). When enabled, the out-of-process |
|
| provider agent serializes CIM instances (contained in get-instance and |
|
| enumerate-instances responses) as XML (embedded in a binary message |
|
| envelope). This improves performance since the server may pass the |
|
| XML instaces through to the requesting client without deserializing them |
|
| from binary and then reserializing them as XML. |
|
| <br> |
|
| <b>Default Value: </b>false<br> |
|
| <b>Recommended Value (Development Build): </b> |
|
| No Specific Recommendation<br> |
|
| <b>Recommended Value (Release Build): </b> |
|
| No Specific Recommendation<br> |
|
| <b>Required: </b>No<br> |
|
| <b>Considerations: </b>This feature has no effect unless the "internal |
|
| binary protocol" feature is enabled (see |
|
| PEGASUS_ENABLE_INTERNAL_BINARY_PROTOCOL). Deciding whether to enable or |
|
| disable this feature is left to the user. Every environment is different |
|
| and some users may prefer lower bandwidth rather than higher performance. |
|
| </ul> |
|
| |
|
| <h5>PEGASUS_ENABLE_EXECQUERY</h5> | <h5>PEGASUS_ENABLE_EXECQUERY</h5> |
| <ul> | <ul> |
| <b>Description: </b>When this environment variable is set, | <b>Description: </b>When this environment variable is set, |
|
|
|
| indication provider.<br> | indication provider.<br> |
| </ul> | </ul> |
| | |
| <h5>PEGASUS_ENABLE_INTERNAL_BINARY_PROTOCOL</h5> |
<h5>PEGASUS_ENABLE_PROTOCOL_INTERNAL_BINARY</h5> |
| <ul> | <ul> |
| <b>Description: </b>If true, OpenPegasus uses a faster binary | <b>Description: </b>If true, OpenPegasus uses a faster binary |
| protocol between the CIM server and provider manager. If false, | protocol between the CIM server and provider manager. If false, |
|
|
|
| <b>Required: </b>No<br> | <b>Required: </b>No<br> |
| <b>Considerations: </b>This option improves performance by optimizing the | <b>Considerations: </b>This option improves performance by optimizing the |
| serialization and deserialization of messages between the server and | serialization and deserialization of messages between the server and |
| out-of-process providers. The binary protocol also supports an optional |
out-of-process providers. |
| "encapsulated XML" feature (see PEGASUS_ENABLE_ENCAPSULATED_XML) for |
<br> |
| details. |
</ul> |
| |
|
| |
<h5>PEGASUS_ENABLE_PROTOCOL_BINARY</h5> |
| |
<ul> |
| |
<b>Description: </b>If true, OpenPegasus uses a faster binary |
| |
protocol between local clients (including the provider agent) 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> | <br> |
| </ul> | </ul> |
| | |
|
|
|
| <b>Recommended Default Value (Release Build): </b>0<br> | <b>Recommended Default Value (Release Build): </b>0<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): </b>No/No<br> | <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/No<br> |
| |
<b>Dynamic?: </b>Yes<br> |
| <b>Considerations: </b>A client connection is considered | <b>Considerations: </b>A client connection is considered |
| idle when it is not in the process of sending a request and | idle when it is not in the process of sending a request and |
| the CIM Server is not processing a request from that connection. | the CIM Server is not processing a request from that connection. |
|
|
|
| considered when configuring an idle connection timeout value. | considered when configuring an idle connection timeout value. |
| The idle connection time is computed using the system clock. | The idle connection time is computed using the system clock. |
| Thus, resetting the system clock may cause unexpected timeout | Thus, resetting the system clock may cause unexpected timeout |
| behavior.<br> |
behavior.This config property can be changed dynamically. The |
| |
changes will apply to all new and existing connections. <br> |
| </ul> | </ul> |
| | |
| <h5>logdir</h5> | <h5>logdir</h5> |
|
|
|
| <b>Recommended Default Value (Release Build):</b> 0<br> | <b>Recommended Default Value (Release Build):</b> 0<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): </b>No/Yes<br> | <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/Yes<br> |
| <b>Dynamic?: </b>No<br> |
<b>Dynamic?: </b>Yes<br> |
| <b>Considerations: </b><br> |
<b>Considerations: </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> | <br> |
| <table border="1" cellspacing="1" bordercolordark="#666666" | <table border="1" cellspacing="1" bordercolordark="#666666" |
| bordercolorlight="#CCCCCC" width=531 | bordercolorlight="#CCCCCC" width=531 |
|
|
|
| $PROVIDERDIRS<br> | $PROVIDERDIRS<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): </b>Yes<br> | <b>Recommend To Be Fixed/Hidden (Release Build): </b>Yes<br> |
| <b>Dynamic?: </b>No<br> |
<b>Dynamic?: </b>Yes<br> |
| <b>Considerations: </b>The CIM Server runs as a privileged | <b>Considerations: </b>The CIM Server runs as a privileged |
| user. And, since Providers run in the same process space as the | user. And, since Providers run in the same process space as the |
| CIM Server, Providers also have privileged access to the | CIM Server, Providers also have privileged access to the |
|
|
|
| 20 (seconds)<br> | 20 (seconds)<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): </b>No/No<br> | <b>Recommend To Be Fixed/Hidden (Release Build): </b>No/No<br> |
| <b>Dynamic?: </b>No<br> |
<b>Dynamic?: </b>Yes<br> |
| |
<b>Considerations: </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: </b> | <b>Source Configuration File: </b> |
| Pegasus/Config/DefaultPropertyTable.h | Pegasus/Config/DefaultPropertyTable.h |
| </ul> | </ul> |
Return to
BuildAndReleaseOptions.html
CVS log
Up to [Pegasus] / pegasus / doc