|
version 1.33, 2012/07/03 11:53:19
|
version 1.34, 2012/07/03 15:23:10
|
|
|
|
| </tbody></table> | </tbody></table> |
| </p></ul> | </p></ul> |
| | |
| |
<h5>hostname</h5> |
| |
<ul> |
| |
<b>Description: </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: </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): </b> |
| |
blank<br> |
| |
<b>Recommended Default Value (Release Build): </b> |
| |
blank<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?: </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: </b> |
| |
Pegasus/Config/DefaultPropertyOwner.cpp |
| |
</ul> |
| |
|
| |
<h5>fullyQualifiedHostName</h5> |
| |
<ul> |
| |
<b>Description: </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: </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): </b> |
| |
blank<br> |
| |
<b>Recommended Default Value (Release Build): </b> |
| |
blank<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?: </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: </b> |
| |
Pegasus/Config/DefaultPropertyOwner.cpp |
| |
</ul> |
| |
|
| <h5>httpPort</h5> | <h5>httpPort</h5> |
| <ul> | <ul> |
| <b>Description: </b>OpenPegasus first attempts to look up the | <b>Description: </b>OpenPegasus first attempts to look up the |
|
|
|
| system. Allowing a registered Provider’s executable to be | system. Allowing a registered Provider’s executable to be |
| replaced with malicious code would result in a critical | replaced with malicious code would result in a critical |
| security defect, giving a malicious user privileged access | security defect, giving a malicious user privileged access |
| to the system. Adminstrators are responsible for ensuring |
to the system. Administrators are responsible for ensuring |
| that only trusted Providers are loaded into providerDir. | that only trusted Providers are loaded into providerDir. |
| In order to simplify the management task associated with | In order to simplify the management task associated with |
| securing Provider executable, the value of providerDir can be | securing Provider executable, the value of providerDir can be |
Return to
BuildAndReleaseOptions.html
CVS log
Up to [Pegasus] / pegasus / doc