iib instance

Overview

This is custom resource which allows you to manage server and broker under specified account in an IBM IIB realm.

Here is an example on how you should use this:

iib_instance { 'IIB107NewInstance':
  ensure         => 'present',
  home_directory => '/opt/ibm/mqsi/iib-10.0.0.7',
  os_user        => 'iibadmin',
}

In this example you are ensuring that instance is present. If the instance is absent the resource creates new istance with specifed user and directory.

Attributes

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_instance

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_instance

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of iib_instance

home_directory

This property allows you to manage path of iib_instance home directory in an IBM IIB realm.

Here is an example on how you should use this:

iib_instance { 'iib8NewInstance':
  ensure         => 'present',
  home_directory => '/opt/ibm/mqsi/iib-10.0.0.8',
}

In this example you are setting the home_directory of IBM IIB 10.0.0 fix pack 8 for selected iib instance.

Back to overview of iib_instance

name

This parameter specifies custom name for iib_instance.

Back to overview of iib_instance

os_user

This property allows you to manage iib_instance admin username in an IBM IIB realm.

Here is an example on how you should use this:

iib_instance { 'iib8NewInstance':
  ensure         => 'present',
  os_user        => 'iibadmin',
}

In this example you are setting the admin user for selected iib instance.

Back to overview of iib_instance

provider

The specific backend to use for this iib_instance 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 configurations

Back to overview of iib_instance

working_directory

This property allows you to manage path of iib_instance working directory in an IBM ACE realm. It is only used in IBM App Connect Enterprise to specify YAML path.

Here is an example on how you should use this:

iib_instance { 'iib8NewInstance':
  ensure         => 'present',
  working_directory => '/var/mqsi/components',
}

In this example you are setting the home_directory of IBM App Connect Enterprise 11.0.0.3 for selected iib instance.

Back to overview of iib_instance