iib property

Overview

This resource allows you to manage brokers and servers in an IBM IIB realm.

This type can be used to construct mqsichangebroker or mqsichangeproperties commands for you setup. This type is a fallback for when the property is not (yet) support on iib_broker or iib_server. Use this type with care.

Here is an example on how to write manifest for global node component value changing:

iib_property {'set_node_cache_policy':
  scope     => 'iib8/NODE1',
  component => 'cachePolicy',
  restart   => true,
  set_value => 'none'
}

Valid global node component names:

• userLilPath
• configurationChangeTimeout
• internalConfigurationTimeout
• httpListenerPort
• statisticsMajorInterval
• ldapPrincipal
• ldapCredentials
• ICU converter path
• userExitPath
• activeUserExits
• function level
• security_status
• cachePolicy
• cachePortRange
• integrationRegistryHostname

Here is an example on how to write manifest for node component that takes objectName:

iib_property {'set_node_cache_policy':
  scope            => 'iib8/NODE1',
  component        => 'webadmins',
  object_name      => 'HTTPConnector',
  object_property  => 'compression',
  restart          => false,
  set_value        => 'on'
}

Make sure that selected node is running before applying manifest.

Valid node component names that take objectName:

• httplistener
• securitycache
• cachemanager
• webadmin
• crlFile

Here is an example on how to write manifest for server property changing:

iib_property {'set_server_accept_count_to_200':
  scope       => 'iib8/NODE1/server_1',
  component   => 'HTTPConnector',
  object_name => 'acceptCount',
  restart     => false,
  set_value   => '200'
}

Attributes

component

This parameter specifies the component of the IIB broker or server you want to manage.

iib_property {‘set_node_cache_policy’: component => ‘NODE/Broker’, }

Back to overview of iib_property

disable_corrective_change

Disable the modification of a resource when Puppet decides it is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the `disable_corrective_change’ parameter, you can disable corrective changes on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ...
  disable_corrective_change => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not modify the resource
and signal an error:

    Error: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/parameter: change from '10' to '20' failed: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change. (corrective)

Back to overview of iib_property

disable_corrective_ensure

Disable the creation or removal of a resource when Puppet decides is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the `disable_corrective_ensure’ parameter, you can disable corrective ensure present or ensure absent actions on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ensure                    => 'present',
  ...
  disable_corrective_ensure => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not create or remove the resource
and signal an error:

    Error: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure.
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/ensure: change from 'absent' to 'present' failed: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure. (corrective)

Back to overview of iib_property

name

This parameter specifies uniqe custom name for iib_property in Puppet realm.

In example

'iib8/NODE1'

Back to overview of iib_property

object_name

This parameter specifies object_name of iib_property in Puppet realm.

In example

'iib8/NODE1'

Back to overview of iib_property

object_property

This parameter specifies the object property you want to manage.

In example

'iib8/NODE1'

Back to overview of iib_property

provider

The specific backend to use for this iib_property resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.Available providers are:

simple

Manage different IIB node configurations

Back to overview of iib_property

restart

Specfies if you want to automaticaly want to stop the broker or the server before applying the value and start again after the change has been applied.

iib_property {'set_node_cache_policy':
  restart   => true,
}

Valid values are true, false.

Back to overview of iib_property

scope

This parameter specifies uniqe custom name for iib_property in Puppet realm.

iib_property {‘set_node_cache_policy’: scope => ‘iib8/NODE1’, }

Back to overview of iib_property

set_value

This parameter specifies the value to set the specfied object property to.

iib_property {‘set_node_cache_policy’: set_value => ‘none’ }

Back to overview of iib_property