Dell Vizioncore Manual de usuario descargar pdf (Pagina 167)

Managing Agents 167

Managing Agent Properties by Type

When an agent connects to the vFoglight Management Server, it is provided with sets of

properties that it uses to configure its correct running state. vFoglight stores agent

properties in the vFoglight Management Server. Any passwords that are defined in

agent properties, and stored in the database, are encrypted. This feature is useful in

situations when a database password is defined in agent properties, you have different

types of databases and their administrators in your environment, such as the vFoglight

database and a production database. Having a database password encrypted prevents

those database administrators that do not interface with vFoglight from accessing the

vFoglight database.

Default versions of these properties are installed with the cartridge in which the agents

are included. You can edit the default properties, create sets of properties that apply

only to a specific agent instance, and create edited clones of property sets that are used

by a subset of the agents of a certain type.

There are two types of agent properties:

• Primary. They are included in the agent component and their settings can be

specific to the agent type or the agent instance. Each agent comes with a set type-

specific properties. You can edit them for a particular agent instance, leave them

unchanged, or apply their settings to all agent instances of the same type. If you

do not change agent properties for an instance, vFoglight uses the default

properties that come with that agent type.

• Secondary. They are in list form. The value of each secondary property can be set

to one or more lists. You will recognize a list-based property by the Edit and

Clone buttons that appear next to it.

Lists that come with an agent type are type-specific and as such global in nature,

which means that any changes to them affect all instances of that agent type. To

override this behavior, you can create an instance-specific list by cloning a global

list and assigning the cloned list to one or more agent instances. Any changes to

this list affect only those agent instances to which the list is assigned.

Examples of situations in which you may want to clone a list include the

following scenarios:

List property

1 2 ... 162 163 164 165 166 167 168 169 170 171 172 ... 530 531

Sin comentarios

Dell Vizioncore Manual de usuario Pagina 167