Table of Contents

1. Overview
2. License
3. Description - What the module does and why it is useful
4. Setup

• Requirements
• Installing the mq_config module

5. Usage - Configuration options and additional functionality
6. Reference - An under-the-hood peek at what the module is doing and how
7. Limitations - OS compatibility, etc.

Overview

This module allows you to configure and manage IBM MQ messaging software. It is part of our family of Puppet modules to install and manage IBM messaging middleware. Besides the mq_config module, this family also contains:

• mq_install to install the MQ software
• iib_config to manage and configure IBM Integration Bus software
• iib_install to install IBM Integration Bus software

Experience the Power of Puppet for IBM MQ

Installing IBM MQ software and managing your IBM MQ configuration can be hard. With Puppet at your side, you get super-powers when installing and managing IBM MQ. If you want to play and experiment with this please take a look at our playgrounds.

License

This is a commercially licensed module. But you can use the module on VirtualBox based development systems for FREE. You can request a FREE trial license here

Check the License for details.

Description

Our mq_config module allows you to configure and manage almost everything you'd want to manage on of an IBM MQ installation. The module allows you to manage:

• mq_authentication_info
• mq_authorization
• mq_certificate
• mq_certificate_file
• mq_channel
• mq_channel_authentication
• mq_key_db
• mq_listener
• mq_manager
• mq_queue
• mq_subscription
• mq_topic
• mq_web

Check here to see the full documentation for this module.

Setup

Requirements

The mq_config module requires:

• Puppet module enterprisemodules-easy_type installed.
• Puppet version 4.0 or higher. Can be Puppet Enterprise or Puppet Open Source
• IBM MQ 8 or 9 installation.
• A valid License from IBM to use this software.
• A valid entitlement for this module by Enterprise Modules.
• Runs on most Linux systems.
• This module supports both Windows and Linux

Installing the mq_config module

To install these modules, you can use a Puppetfile

mod 'enterprisemodules/mq_config'               ,'1.0.x'

Then use the librarian-puppet or r10K to install the software.

You can also install the software using the puppet module command:

puppet module install enterprisemodules-mq_config

Usage

Building a total MQ setup requires quite some work. To help you, we have built some examples:

• MQ only example
• MQ and IIB example

Thes repos contain examples of how you can install and configure a basic MQ setup.

Reference

Here you can find some more information regarding this puppet module:

• The MQ config documentation
• The product announcement

Here is a list of related blog posts:

• Introducing the IBM MQ Puppet module

Some example code:

• Simple MQ demo
• MQ and IIB demo

Limitations

This module runs most Linux versions. It requires a puppet version higher than 4. Contact us of you need to run this module on other flavors of UNIX. We can work together with you to make it work.

Reference

Table of Contents

Resource types

• mq_authentication_info: This resource allows you to manage MQ authorization Information Objects. Here is an example on how you should use this: mq_authenticati
• mq_authorization: This resource allows you to manage a MQ autorizations. Here is an example on how you should use this: mq_authorization { "group/mymqgro
• mq_certificate: This resource allows you to manage SSL Certificates for MQ in a database. It allows multiple operations: 1) Adding a certificate from an as
• mq_certificate_file: Extracts individual certificates from a certificate key database. Depending on the value f the type parameter, different actions will be d
• mq_channel: This resource allows you to manage a MQ Channel. Here is an example on how you should use this with the CHLTYPE in the name: mq_chann
• mq_channel_authentication: This resource allows you to manage a MQ Channel authenticatio record. Here is an example on how you should use this: mq_channel_authe
• mq_key_db: This resource allows you to manage a MQ key database. Here is an example on how you should use this: mqkey_db {'/var/mqm/keys/test_db
• mq_listener: This resource allows you to manage a MQ listener. Here is an example on how you should use this: mq_listener { 'IIB10QM/SYSTEM.DEFAULT.L
• mq_manager: This resource allows you to manage a MQ queue manager. Here is an example on how you should use this: mq_manager { 'QM1': ensure
• mq_queue: This resource allows you to manage a MQ queue. Here is an example on how you should use this with QTYPE in the name: mq_queue { 'QM1/QL
• mq_subscription: This resource allows you to manage a MQ topic. Here is an example on how you should use this: mq_subscription { 'QUEUENAME/SUBNAME':
• mq_topic: This resource allows you to manage a MQ topic. Here is an example on how you should use this: mq_topic { 'QM1/EM_TEST_TOPIC': ens
• mq_web: This resource allows you to manage the MQ Web package. This is a singleton resource. So there is always only one resource available on the sy

Functions

• mq_config::is_standby: See the file "LICENSE" for the full license governing this code. Function to fetch the fact mq_managers and based on that information decid
• mq_config::qmgrs_in: See the file "LICENSE" for the full license governing this code. Function to fetch the fact mq_managers and based on that information decid
• mq_config::resources_for: See the file "LICENSE" for the full license governing this code. Function to fetch the fact mq_managers and based on that information decid

Tasks

• manager: Allows get the status, create or remove an MQ Queue manager
• queue: Allows get the status, create or remove MQ Queue
• topic: Allows get the status, create or remove MQ topic

Resource types

mq_authentication_info

This resource allows you to manage MQ authorization Information Objects.

Here is an example on how you should use this:

mq_authentication_info { 'QM1/CRLLDAP/MY_LDAP':
  ensure   => 'present',
}

Properties

The following properties are available in the mq_authentication_info type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_authentication_info type.

• provider

provider

The specific backend to use for this mq_authentication_info resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_authorization

This resource allows you to manage a MQ autorizations.

Here is an example on how you should use this:

mq_authorization { "group/mymqgroup->MYQM1/qmgr/self":
  ensure    => 'present',
  authority => ['allmqi', 'dlt', 'chg', 'dsp', 'ctrl', 'system'],
}

Properties

The following properties are available in the mq_authorization type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_authorization type.

• provider

provider

The specific backend to use for this mq_authorization resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_certificate

This resource allows you to manage SSL Certificates for MQ in a database.

It allows multiple operations:

1) Adding a certificate from an ascii of binary file 2) Importing a labeled certificate from an other certificate database 3) Creating a self signed certificate

Option 1: Adding a certificate from an ascii of binary file

Puppet uses this action when the source parameter is specified and the specified source_type is either ascii or binary. Here is an example on how to use this:

mq_certificate {'/var/mqm/keys/test_db_2.kdb:my_label_1':
  ensure          => 'present',
  password        => 'verysecret',
  source          => '/var/mqm/keys/my_label_2.ascii',
  source_type     => 'ascii',
}

Option 2: Importing a labeled certificate from an other certificate database

Puppet uses this action when the source parameter is specified and the specified source_type is:

• cms
• kdb
• pkcs12
• p12
• pkcs7
• pem

Here is an example on how to use this:

mq_certificate {'/var/mqm/keys/test_db_2.kdb:my_label_1':
  ensure          => 'present',
  password        => 'verysecret',
  source          => '/var/mqm/keys/my_label_1.p12',
  source_type     => 'p12',
  source_label    => 'my_label_1',
  source_password => 'verysecret',
}

Option 3: Creating a self signed certificate.

When no source value is given, Puppet creates a self signed cerificate withe the specified label inside of the certificate database. Here is an example on how that works:

mq_certificate {'/var/mqm/keys/test_db_1.kdb:my_label_1':
  ensure             => 'present',
  password           => 'verysecret',
  distinguished_name => 'cn=bert.....',
}

Properties

The following properties are available in the mq_certificate type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_certificate type.

• provider

provider

The specific backend to use for this mq_certificate resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_certificate_file

Extracts individual certificates from a certificate key database.

Depending on the value f the type parameter, different actions will be done.

• When the type is either ascii of binary a certificate file will be created
• When the type is one of: cms,kdb,pkcs12,p12,pkcs7,pem a certificate database of the specified type will be created and the certificate with the specified label will be added to it.

Here is an example on how you can use this:

mq_certificate_file {'/var/mqm/keys/my_label_1.p12':
  ensure          => 'present',
  ource_type      => 'p12',
  key_db          => '/var/mqm/keys/test_db_1.kdb',
  label           => 'my_label_1',
  type            => 'p12',
  password        => 'verysecret',
  target_password => 'verysecret',
}

Properties

The following properties are available in the mq_certificate_file type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_certificate_file type.

• provider

provider

The specific backend to use for this mq_certificate_file resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_channel

This resource allows you to manage a MQ Channel.

Here is an example on how you should use this with the CHLTYPE in the name:

  mq_channel { 'QM1/RCVR/EM_TEST_CHANNEL':
    ensure   => 'present',
    comphdr  => 'NONE',
    compmsg  => 'NONE',
    hbint    => '320',
    kaint    => 'AUTO',
    maxmsgl  => '4194304',
    monchl   => 'QMGR',
    npmspeed => 'FAST',
    seqwrap  => '999999999',
    sslcauth => 'REQUIRED',
    statchl  => 'QMGR',
    trptype  => 'TCP',
    usedlq   => 'YES',
  }

Here is an deprecated example on how you should use this:

  mq_channel { 'QM1/EM_TEST_CHANNEL':
    ensure   => 'present',
    chltype  => 'RCVR',
    comphdr  => 'NONE',
    compmsg  => 'NONE',
    hbint    => '320',
    kaint    => 'AUTO',
    maxmsgl  => '4194304',
    monchl   => 'QMGR',
    npmspeed => 'FAST',
    seqwrap  => '999999999',
    sslcauth => 'REQUIRED',
    statchl  => 'QMGR',
    trptype  => 'TCP',
    usedlq   => 'YES',
  }

Properties

The following properties are available in the mq_channel type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_channel type.

• provider

provider

The specific backend to use for this mq_channel resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_channel_authentication

This resource allows you to manage a MQ Channel authenticatio record.

Here is an example on how you should use this:

  mq_channel_authentication { 'QM1/EM_TEST_CHANNEL':
    ensure   => 'present',
      ...
  }

When used for ADDRESMAP records the syntax is:

mq_channel_authentication { 'QM1/ADRESSMAP/ADMIN/10.2.248.*':
  ensure   => 'present',
  mcauser  => 'my_user',
}

Properties

The following properties are available in the mq_channel_authentication type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_channel_authentication type.

• provider

provider

The specific backend to use for this mq_channel_authentication resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_key_db

This resource allows you to manage a MQ key database.

Here is an example on how you should use this:

mq_key_db {'/var/mqm/keys/test_db_1.kdb':
  ensure   => 'present',
  stashed  => true,
  password => 'verysecret'
}

Properties

The following properties are available in the mq_key_db type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_key_db type.

• provider

provider

The specific backend to use for this mq_key_db resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_listener

This resource allows you to manage a MQ listener.

Here is an example on how you should use this: mq_listener { 'IIB10QM/SYSTEM.DEFAULT.LISTENER.TCP': ensure => 'present', backlog => '0', control => 'MANUAL', port => '0', trptype => 'TCP', }

Properties

The following properties are available in the mq_listener type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_listener type.

• provider

provider

The specific backend to use for this mq_listener resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_manager

This resource allows you to manage a MQ queue manager.

Here is an example on how you should use this:

mq_manager { 'QM1':
  ensure   => 'present',
  acctcono => 'DISABLED',
  acctint  => '1800',
  acctmqi  => 'OFF',
  acctq    => 'OFF',
  activrec => 'MSG',
  actvcono => 'DISABLED',
  actvtrc  => 'OFF',
  authorev => 'DISABLED',
  ccsid    => '1208',
  certlabl => 'ibmwebspheremqqm1',
  certvpol => 'ANY',
  chad     => 'DISABLED',
  chadev   => 'DISABLED',
  chlauth  => 'ENABLED',
  chlev    => 'DISABLED',
  clwllen  => '100',
  clwlmruc => '999999999',
  clwluseq => 'LOCAL',
  cmdev    => 'DISABLED',
  configev => 'DISABLED',
  connauth => 'SYSTEM.DEFAULT.AUTHINFO.IDPWOS',
  defclxq  => 'SCTQ',
  inhibtev => 'DISABLED',
  ipaddrv  => 'IPV4',
  localev  => 'DISABLED',
  loggerev => 'DISABLED',
  markint  => '5000',
  maxhands => '256',
  maxmsgl  => '4194304',
  maxpropl => 'NOLIMIT',
  maxumsgs => '10000',
  monacls  => 'QMGR',
  monchl   => 'OFF',
  monq     => 'OFF',
  perfmev  => 'DISABLED',
  psclus   => 'ENABLED',
  psmode   => 'ENABLED',
  psnpmsg  => 'DISCARD',
  psnpres  => 'NORMAL',
  psrtycnt => '5',
  pssyncpt => 'IFPER',
  remoteev => 'DISABLED',
  revdns   => 'ENABLED',
  routerec => 'MSG',
  schinit  => 'QMGR',
  scmdserv => 'QMGR',
  sslev    => 'DISABLED',
  sslfips  => 'NO',
  sslkeyr  => '/var/mqm/qmgrs/QM1/ssl/key',
  sslrkeyc => '0',
  statacls => 'QMGR',
  statchl  => 'OFF',
  statint  => '1800',
  statmqi  => 'OFF',
  statq    => 'OFF',
  status   => 'Running',
  strstpev => 'ENABLED',
  suiteb   => 'NONE',
  treelife => '1800',
  trigint  => '999999999',
}

Properties

The following properties are available in the mq_manager type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_manager type.

• provider

provider

The specific backend to use for this mq_manager resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_queue

This resource allows you to manage a MQ queue.

Here is an example on how you should use this with QTYPE in the name:

mq_queue { 'QM1/QLOCAL/EM_TEST':
  ensure   => 'present',
  acctq    => 'QMGR',
  bothresh => '0',
  clwlprty => '4',
  clwlrank => '1',
  clwluseq => 'QMGR',
  defbind  => 'OPEN',
  defpresp => 'SYNC',
  defprty  => '0',
  defpsist => 'NO',
  defreada => 'NO',
  defsopt  => 'SHARED',
  distl    => 'NO',
  get      => 'ENABLED',
  maxdepth => '5000',
  maxmsgl  => '4194304',
  monq     => 'QMGR',
  msgdlvsq => 'PRIORITY',
  npmclass => 'NORMAL',
  propctl  => 'COMPAT',
  put      => 'ENABLED',
  qdepthhi => '80',
  qdepthlo => '20',
  qdphiev  => 'DISABLED',
  qdploev  => 'DISABLED',
  qdpmaxev => 'ENABLED',
  qsvciev  => 'NONE',
  qsvcint  => '999999999',
  retintvl => '999999999',
  scope    => 'QMGR',
  statq    => 'QMGR',
  trigdpth => '1',
  trigmpri => '0',
  trigtype => 'FIRST',
  usage    => 'NORMAL',
}

Here is an deprecated example on how you should use this:

mq_queue { 'QM1/EM_TEST':
  ensure   => 'present',
  acctq    => 'QMGR',
  bothresh => '0',
  clwlprty => '4',
  clwlrank => '1',
  clwluseq => 'QMGR',
  defbind  => 'OPEN',
  defpresp => 'SYNC',
  defprty  => '0',
  defpsist => 'NO',
  defreada => 'NO',
  defsopt  => 'SHARED',
  distl    => 'NO',
  get      => 'ENABLED',
  maxdepth => '5000',
  maxmsgl  => '4194304',
  monq     => 'QMGR',
  msgdlvsq => 'PRIORITY',
  npmclass => 'NORMAL',
  propctl  => 'COMPAT',
  put      => 'ENABLED',
  qdepthhi => '80',
  qdepthlo => '20',
  qdphiev  => 'DISABLED',
  qdploev  => 'DISABLED',
  qdpmaxev => 'ENABLED',
  qsvciev  => 'NONE',
  qsvcint  => '999999999',
  qtype    => 'QLOCAL',
  retintvl => '999999999',
  scope    => 'QMGR',
  statq    => 'QMGR',
  trigdpth => '1',
  trigmpri => '0',
  trigtype => 'FIRST',
  usage    => 'NORMAL',
}

Properties

The following properties are available in the mq_queue type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_queue type.

• provider

provider

The specific backend to use for this mq_queue resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_subscription

This resource allows you to manage a MQ topic.

Here is an example on how you should use this:

mq_subscription { 'QUEUENAME/SUBNAME':
  ensure   => 'present',
  topicstr => 'b_topic',
  dest     => 'QUEUENAME',
}

mq_subscription {'QM1/SUB1':
  ensure   => 'present',
  dest     => 'SYSTEM.DEFAULT.REMOTE.QUEUE',
  topicstr => 'SYSTEM.DEFAULT.TOPIC'
}

Properties

The following properties are available in the mq_subscription type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_subscription type.

• provider

provider

The specific backend to use for this mq_subscription resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_topic

This resource allows you to manage a MQ topic.

Here is an example on how you should use this:

mq_topic { 'QM1/EM_TEST_TOPIC':
  ensure   => 'present',
  topicstr => 'b_topic',
  defprty  => '5',
  defpsist => 'ASPARENT',
  dursub   => 'ASPARENT',
  mcast    => 'ASPARENT',
  npmsgdlv => 'ASPARENT',
  pmsgdlv  => 'ASPARENT',
  proxysub => 'FIRSTUSE',
  pub      => 'ASPARENT',
  pubscope => 'ASPARENT',
  sub      => 'ASPARENT',
  subscope => 'ASPARENT',
  ttype    => 'LOCAL',
  usedlq   => 'ASPARENT',
  wildcard => 'PASSTHRU',
}

Properties

The following properties are available in the mq_topic type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_topic type.

• provider

provider

The specific backend to use for this mq_topic resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

mq_web

This resource allows you to manage the MQ Web package. This is a singleton resource. So there is always only one resource available on the system and it is called mqweb. Here is an example on how you should use this:

mq_web { 'mqweb':
  ensure                                   => 'present',
  http_host                                => 'localhost',
  http_port                                => -1,
  https_port                               => 9443,
  ltpa_cookie_name                         => 'LtpaToken2_${env.MQWEB_LTPA_SUFFIX}',
  ltpa_expiration                          => 120,
  max_msg_trace_file_size                  => 200,
  max_msg_trace_files                      => 5,
  max_trace_file_size                      => 20,
  max_trace_files                          => 10,
  mq_console_autostart                     => true,
  mq_rest_autostart                        => false,
  mq_rest_cors_max_age_in_seconds          => 0,
  mq_rest_csrf_validation                  => true,
  mq_rest_gateway_enabled                  => true,
  mq_rest_messaging_enabled                => true,
  mq_rest_mft_enabled                      => false,
  mq_rest_mft_reconnect_timeout_in_minutes => 30,
  mq_rest_request_timeout                  => 30,
  secure_ltpa                              => true,
  status                                   => 'stopped',
  trace_spec                               => '*=info',
}

Properties

The following properties are available in the mq_web type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the mq_web type.

• provider

provider

The specific backend to use for this mq_web resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

Functions

mq_config::is_standby

Type: Ruby 4.x API

See the file "LICENSE" for the full license governing this code.

Function to fetch the fact mq_managers and based on that information decide if the specfied queue manager is running in standby mode or not.

mq_config::is_standby(String $manager)

See the file "LICENSE" for the full license governing this code.

Function to fetch the fact mq_managers and based on that information decide if the specfied queue manager is running in standby mode or not.

Returns: Any

manager

Data type: String

mq_config::qmgrs_in

Type: Ruby 4.x API

See the file "LICENSE" for the full license governing this code.

Function to fetch the fact mq_managers and based on that information decide if the specfied queue manager is running in standby mode or not.

mq_config::qmgrs_in(Hash $resources)

See the file "LICENSE" for the full license governing this code.

Function to fetch the fact mq_managers and based on that information decide if the specfied queue manager is running in standby mode or not.

Returns: Array

resources

Data type: Hash

mq_config::resources_for

Type: Ruby 4.x API

See the file "LICENSE" for the full license governing this code.

Function to fetch the fact mq_managers and based on that information decide if the specfied queue manager is running in standby mode or not.

mq_config::resources_for(Hash[String,Hash] $resources, String $manager)

See the file "LICENSE" for the full license governing this code.

Function to fetch the fact mq_managers and based on that information decide if the specfied queue manager is running in standby mode or not.

Returns: Any

resources

Data type: Hash[String,Hash]

manager

Data type: String

Tasks

manager

Allows get the status, create or remove an MQ Queue manager

Supports noop? false

Parameters

action

Data type: Optional[Enum['list', 'status','create','remove']]

The action you want to execute

queue_manager_name

Data type: Optional[String[1]]

The name of the queue manager to use.

properties

Data type: Optional[Hash]

The properties to use when create a queue manager

queue

Allows get the status, create or remove MQ Queue

Supports noop? false

Parameters

action

Data type: Optional[Enum['list', 'status','create','remove']]

The action you want to execute

queue_name

Data type: Optional[String[1]]

The name of the queue to use.

properties

Data type: Optional[Hash]

The properties to use when create a queue

topic

Allows get the status, create or remove MQ topic

Supports noop? false

Parameters

action

Data type: Optional[Enum['list', 'status','create','remove']]

The action you want to execute

topic_name

Data type: Optional[String[1]]

The name of the topic to use.

properties

Data type: Optional[Hash]

The properties to use when create a topic

History

20-06-2023 Version 1.16.0

• [core] Add support for Ruby 3.2and Puppet 8

03-11-2022 Version 1.15.0

• [core] Add support for EL 9

17-03-2022 Version 1.14.0

• [release] Add support for AlmaLinux and Rocky

30-09-2021 Version 1.13.6

• [core] Fix ruby 2.5 incompatibility

31-08-2021 Version 1.13.5

• [core] Fix confinement on AIX

30-08-2021 Version 1.13.4

[tasks] Update to use latest Bolt API and add acc. tests [doc] Updated docs and REFERENCE.md

27-07-2021 Version 1.13.3

• [docs] Update description to contain all types
• [core] Add confinement until MQ installed

23-07-2021 Version 1.13.2

• [mq_manager] Fix detection of systemctl usage

21-12-2020 Version 1.13.1

• [core] Fix ruby 2.7 issue

21-12-2020 Version 1.13.0

• [release] Add puppet 7 to the list of supported versions

08-06-2020 Version 1.12.5

• [mq_certificate] Don’t use runmqakm anymore.

04-06-2020 Version 1.12.4

• [mq_certificate] Add tmp_dir parameter

03-06-2020 Version 1.12.3

• [mq_certificate] Fix adding pem certificates

25-05-2020 Version 1.12.2

• [mq_certificate] Handle stashed passwords

29-04-2020 Version 1.12.1

• [mq_manager] Losen property checks on ccsid

25-03-2020 Version 1.12.0

• [mq_certificate_file] initial implementation
• [mq_certificate] Initial implementation
• [mq_key_db] Initial implemenation

25-03-2020 Version 1.11.9

• [mq_manager] Fix connauth property with empty values

24-03-2020 Version 1.11.8

• [mq_queue] Make target property case insensitive
• [mq_manager] skip property changes when queue in standby mode

21-03-2020 Version 1.11.7

• [mq_manager] Fix removal of standby queue managers
• [mq_manager] Fix issues when queuemanager contains special characters

11-03-2020 Version 1.11.6

• [core] Fix for case sensitive names

10-03-2020 Version 1.11.5

• [facts/mq_manager] Only run the fact when dspmq command is available
• [facts] Add the mq_path fact

03-03-2020 Version 1.11.4

• [mq_manager] Fix typo

03-03-2020 Version 1.11.3

• [mq_manager] Fix typo

03-03-2020 Version 1.11.2

• [mq_manager] Fix standby parameter
• [mq_manager] Fix start and stop when running under systemd

13-02-2020 Version 1.11.1

• [mq_channel] Make checks less restrictive
• [mq_channel] Fix identical channel names with different types
• [mq_authorization] Remove system from the list of none supprted generic authorizations
• [core] Fix quoted array properties

04-11-2019 Version 1.11.0

• [release] Add RHEL8 support and sanetize supported OS-es
• [core] Add AIX support

23-08-2019 Version 1.10.0

• [mq_topic] Fix data type for topicstr
• [mq_manager] Make multi_instance property a boolean
• [core] Make string data_type more strict
• [core] Use real data types for properties and parameters

09-04-2019 Version 1.9.0

• [core] Add support for Windows

09-04-2019 Version 1.8.0

• [mq_subscription] Initial implementation

08-03-2019 Version 1.7.6

• [mq_channel] Add support for value AUTO for property kaint
• [mq_manager] Fix for usage with Puppet 6

29-01-2019 Version 1.7.5

• [mq_channel] Fix CLNTCONN and CLUSSDR channles
• [mq_channel] Fix SVRCONN channels
• [mq_channel] Fix symbol issues
• [core] Fix symbol issues
• [mq_authorization] Fix symbol issues
• [mq_channel] Fix symbol issues
• [mq_channel_authentication] Fix symbol issues

06-01-2019 Version 1.7.4

• [mq_web] Make status property more resiliant for multiple puppet versions
• [mq_listener] Make status property more resiliant for multiple puppet versions

06-01-2019 Version 1.7.3

• Fix release error

05-01-2019 Version 1.7.2

• [mq_manager] Make status property more resiliant for multiple puppet versions

14-11-2018 Version 1.7.1

• [mq_channel] Fix removeal of clnttbl channels
• [mq_listener] Fix acceptance test and destroying listener

5-11-2018 Version 1.7.0

• [mq_listener] Fix acceptance test for port property
• [mq_manager] Add support for more logging methods
• [mq_listener] Stop listener before removing it
• [mq_manager] Add support for logging parameter
• [mq_manager] Fix error in absenting queue manager
• [core] Better handling of strange characters in properties an overlapping property names
• [mq_channel_authentication] Fetch full index in first pass
• [mq_ channel_authentication] Fix when no records are available
• [core] Add allowed_exits support to mqsc commands
• [mq_manager] Add support for logfile pages
• [mq_manager] Add support for specifying queue manager als default queue manager

22-10-2018 Version 1.6.0

• [mq_channel_authentication] Add support for multiple ADDRESSMAP record

11-10-2018 Version 1.5.0

• [core] Fix sslpeer and missing quotes errors
• [mq_channel] Fix small glitch in channel name
• [mq_queue] Change qtype to parameter
• [mq_channel] Change chltype to parameter
• [mq_queue] Add QTYPE to the name of mq_queue
• [mq_channel] Add backwards compatibility with naming
• [mq_channel] Leave only property chltype for channel name

11-10-2018 Version 1.4.0

• [web_property] Initial implementation

25-09-2018 Version 1.3.4

• [mq_authentication_info] Fix bug when MQ uses different seperation between records

24-09-2018 Version 1.3.3

• [mq_channel] Add some morte acceptance tests
• [mq_channel] Fix trptype property
• [acceptance] Use Puppet 6 for acceptance tests

17-09-2018 Version 1.3.2

• [core] Add unittests with Puppet 6.0.0
• [mq_channel] Raise a error when we try to change the channel type.

17-09-2018 Version 1.3.1

• [mq_authorization] Better error messages when invalid entity string
• [mq_manager] refresh security after changes in connauth

1-09-2018 Version 1.3.0

• [core] Handle creation and modification call’s when QM is not running
• [mq_topic] Fix typo
• [resources_for] Initial implementation
• [qmgrs_in] Initial implementation
• [mq_manager] Running in standby is valid running mode
• [core] Only fetch info from running queue managers
• [resources_for] Initial implementation
• [is_standby] Initial implementation of function
• [facts] Add fact describing queue managers
• [mq_manager] Skip repos acceptance test for now

07-09-2018 Version 1.2.1

• [core] Add support for other MQ manager statusses
• [core] Add support for allowed_exits

04-09-2018 Version 1.2.0

[mq_manager] Add standby parameter for use on 2nd manager on standby node

29-07-2018 Version 1.1.0

• [mq_channel_authentication] Initial implementation

07-07-2018 Version 1.0.13

• [mq_manager] fix datapath implementation

04-07-2018 Version 1.0.12

• [mq_manager] Add support for multi-instance queue managers

27-06-2018 Version 1.0.11

• [core] Change the mq_authorization type to fetch properly
• [mq_authorization] Fix bug when no authorities are found
• [mq_channel] Fix typo in acceptance test description
• [release] Better description in the metadata

09-02-2018 Version 1.0.10

• [tasks] Add first set of tasks for often used resources
• [mq_manager] Fix documentation
• [release] Fix link to license in readme

26-01-2018 Version 1.0.9

• [release] Added license notice

26-01-2018 Version 1.0.8

• [release] Add license text and readme
• [docs] Update documentation

09-01-2018 Version 1.0.7

• [mq_listener] Add status field for starting and stopping
• [mq_authentication_info] Fix some property data types
• [mq_listener] Add case sensitivity to desc property
• [mq_channel] Add extra checks on valid combinations of properties
• [mq_channel] Fix some properties
• [mq_topic] Fix some properties
• [mq_topic] Fix some properties and updating of topics
• [mq_manager] Fix validation and case sensitivity of multiple properties

05-01-2018 Version 1.0.6

• [mq_authorization] Allow authority with value [none]
• [mq_listener] Fix creation error’s

03-01-2018 Version 1.0.5

• [mq_topic] Add check for required property topicstr
• [mq_channel] Add check for required property chltype
• [mq_queue] Add check on required property qtype
• [mq_listener] Initial implementation
• [mq_authorization] Check and reject usage of generic authorities
• [mq_authorization] Fix error when managing queue manager
• [mq_authorization] Fix setting when wildcard definition
• [mq_channel] Remove non US-ASCII character

28-12-2017 Version 1.0.4

• [mq_authorization] Quote object names
• [mq_authentication_info] Initial implementation
• [mq_authorization] Initial implementation

06-11-2017 Version 1.0.3

• [core] Don’t cd to current_working directory when executing cmd

13-09-2017 Version 1.0.2

• [core] Fix encoding to utf8

14-07-2017 Version 1.0.1

• [core] use mqm instead of mquser

19-05-2017 Version 1.0.0

• Initial release