pegasus/doc/BuildAndReleaseOptions.html - diff

Return to BuildAndReleaseOptions.html CVS log

Up to [Pegasus] / pegasus / doc

Diff for /pegasus/doc/BuildAndReleaseOptions.html between version 1.5 and 1.15

version 1.5, 2008/10/14 17:15:34

version 1.15, 2009/05/27 05:56:21

Line 730

indication provider.

</ul>

<h5>PEGASUS_ENABLE_PROTOCOL_INTERNAL_BINARY</h5>

<ul>

Description: If true, OpenPegasus uses a faster binary

protocol between the CIM server and provider manager. If false,

OpenPegasus uses the older XML-based protocol instead.

Default Value: true

Recommended Value (Development Build): true

Recommended Value (Release Build): true

Required: No

Considerations: This option improves performance by optimizing the

serialization and deserialization of messages between the server and

out-of-process providers.

</ul>

<h5>PEGASUS_ENABLE_PROTOCOL_BINARY</h5>

<ul>

Description: 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.

Default Value: false

Recommended Value (Development Build): false

Recommended Value (Release Build): false

Required: No

Considerations: This option improves performance by using a faster

binary protocol between local clients and the CIM server.

</ul>

<h5>PEGASUS_ENABLE_INTEROP_PROVIDER</h5>

<ul>

Description: If true, the OpenPegasus Interop Provider

Line 1658

Line 1690

titled "Configuration Properties" for additional detail.

</ul>

<h5>PEGASUS_USE_SQLITE_REPOSITORY</h5>

<ul>

Description: If true, new repository stores are created

using a SQLite database. Existing file-based stores will continue

to be recognized and operate seamlessly.

Default Value: false

Recommended Value (Development Build): true

Recommended Value (Release Build): true

Required: No

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

Description: If set, OpenPegasus will be built

Line 1688

Line 1736

compiler version < 1300.

</ul>

<h5>SQLITE_HOME</h5>

<ul>

Description: 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.

Default Value: Not Set

Recommended Value (Development Build):

No Specific Recommendation

Recommended Value (Release Build):

No Specific Recommendation

Required: Yes, if PEGASUS_USE_SQLITE_REPOSITORY is set to true

and the SQLite files are not installed in locations that are searched by

default.

Considerations: This environment variable is only used if

PEGASUS_USE_SQLITE_REPOSITORY is set to true.

</ul>

<h4>Examples Building a Linux IA32 (#IA64) Development/Debug Version</h4>

<ul>

export PEGASUS_ROOT=/home/pegasusbld/pegasus

Line 2105

Line 2170

Recommended Default Value (Release Build): true

Recommend To Be Fixed/Hidden (Development Build): No/No

Recommend To Be Fixed/Hidden (Release Build): No/No

Dynamic?: No

Dynamic?: Yes/No

Considerations: 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.

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

bordercolorlight="#CCCCCC" width=531

Line 2160

Line 2249

Recommended Default Value (Release Build): false

Recommend To Be Fixed/Hidden (Development Build): No/No

Recommend To Be Fixed/Hidden (Release Build): No/No

Dynamic?: No

Dynamic?: Yes

Considerations:

<ul>

<li>Any errors encountered during normalization result in a

Line 2504

Line 2593

Recommended Default Value (Release Build): 0

Recommend To Be Fixed/Hidden (Development Build): No/No

Recommend To Be Fixed/Hidden (Release Build): No/No

Dynamic?: Yes

Considerations: 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.

Line 2516

Line 2606

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.

behavior.This config property can be changed dynamically. The

changes will apply to all new and existing connections.

</ul>

<h5>logdir</h5>

Line 2575

Line 2666

Recommended Default Value (Release Build): 0

Recommend To Be Fixed/Hidden (Development Build): No/No

Recommend To Be Fixed/Hidden (Release Build): No/Yes

Dynamic?: No

Dynamic?: Yes

Considerations:

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

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

bordercolorlight="#CCCCCC" width=531

Line 2630

Line 2724

$PROVIDERDIRS

Recommend To Be Fixed/Hidden (Development Build): No/No

Recommend To Be Fixed/Hidden (Release Build): Yes

Dynamic?: No

Dynamic?: Yes

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

Line 2822

Line 2916

20 (seconds)

Recommend To Be Fixed/Hidden (Development Build): No/No

Recommend To Be Fixed/Hidden (Release Build): No/No

Dynamic?: No

Dynamic?: Yes

Considerations: Any changes made to this config property

dynamically will apply to new CIM Server connections only

keeping old already established connections unchanged.

Source Configuration File:

Pegasus/Config/DefaultPropertyTable.h

</ul>

Line 2960

Line 3057

<ul>

Description: Defines the desired facility for trace

messages. Valid values include: "File"

and "Log".

, "Log" and "Memory" .

Default Value: File

Recommended Default Value (Development Build): File

Recommended Default Value (Release Build): File

Line 2972

Line 3069

trace messagesare written into the file specified by the

configuration option traceFilePath. If you specify

"Log", trace messages are written to the

OpenPegasus Log.

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

Source Configuration File:

Pegasus/Config/TracePropertyOwner.cpp

</ul>

Line 3007

Line 3109

Pegasus/Config/TracePropertyOwner.cpp

</ul>

<h5>traceMemoryBufferKbytes</h5>

<ul>

Description: Defines the size of the buffer for

in memory tracing in kbytes ( 210 bytes ).

Smallest value is 16.

Default Value: 10240

Recommended Default Value (Development Build): 10240

Recommended Default Value (Release Build): 10240

Recommend To Be Fixed/Hidden (Development Build): No/No

Recommend To Be Fixed/Hidden (Release Build): No/No

Dynamic?: No

Case Sensitive?: No

Considerations: Is ignored if configuration

property traceFacility is not set to Memory.

Source Configuration File:

Pegasus/Config/TracePropertyOwner.cpp

</ul>

<h3>Configuration Constants</h3>

<h4>Definitions</h4>

Line 3203

Line 3323

</ul>

<hr>

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

agreements. Refer to the OpenPegasusNOTICE.txt file distributed with

Company, L.P.; IBM Corp.; The Open Group; VERITAS Software Corporation

this work for additional information regarding copyright ownership.

Each contributor licenses this file to you under the OpenPegasus Open

EMC Corporation; Symantec Corporation; The Open Group.

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

License.

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

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

obtaining a copy  of this software and associated documentation files

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

(the "Software"), 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:

furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included

in all copies or substantial portions of the Software.

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED

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  "AS IS", 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.

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.

<hr>

Template last modified: January 20th 2004 by Martin Kirk Template version: 1.6

</body>

</html>

Legend:

Removed from v.1.5
changed lines
	Added in v.1.15

No CVS admin address has been configured