IBM MQ Virtual System Pattern Type software components

Software components provide function in your patterns. You can configure components to create an IBM® MQ environment that is fully operational when you deploy your pattern in the cloud. You can change the properties when you configure or deploy a pattern, and by running a script.

Component configuration parameters

The following table contains component configuration parameters for IBM MQ Virtual System Pattern Type:

Table 1. Component configuration parameters.
Label	Description
Type of IBM MQ configuration	Determines what type of queue manager is created after IBM MQ has been installed on the system. Installation only: no queue manager is created and all subsequent parameters are ignored. Single instance: a single instance queue manager is created, using the following parameters. High availability active instance: a multi-instance active queue manager is created, using the following parameters. High availability standby instance: a multi-instance standby queue manager is created, using the following parameters.
Queue manager name	The name of the queue manager. This is required if Type of IBM MQ configuration is not Installation only. To avoid confusion, make this name unique in your network.
Queue manager description	A description of the queue manager.
Listener port	The TCP/IP listener port number. This is required if Type of IBM MQ configuration is not Installation only.
Dead letter queue	The queue manager dead-letter queue.
Queue manager uses linear logging?	Determines whether the queue manager uses linear logging. If false is specified, circular logging is used.
Queue manager log pages	The number of queue manager log pages.
Primary logs	The number of primary IBM MQ log files.
Secondary Logs	The number of secondary IBM MQ log files.
Log path	The file system directory for log data.
Data path	The file system directory for queue manager data.
Error path	The file system directory for error data.
Shared directory	The shared directory in which data and log files are stored. The queue manager must have read and write authorization. This value must be set if Type of IBM MQ configuration is set to High availability active instance or High availability standby instance.
Queue manager directory	The name of the queue manager data directory. Sometimes it is different from the queue manager name. The rules for transforming queue manager names into directory names are described in Understanding IBM MQ file names. This value must be set if Type of IBM MQ configuration is set to High availability active instance.
Manage IBM MQ data manually	You can choose to manage your data manually. This option ensures that your IBM MQ data is not deleted when the deployed instance is deleted, provided that the location you choose for your data is away from the deployed pattern instance, for example, on the shared GPFS server. If the option to manage the IBM MQ data directory is not selected, the deployment id is used in the IBM MQ data path at the time of instance creation. When the instance is deleted, the IBM MQ data is deleted too.
Use existing IBM MQ queue manager data directory	You can deploy an instance from a pattern and use data that exists from a previous instance to re-create and resume the IBM MQ queue manager.
Do not install IBM MQ Advanced components	You can choose not to install IBM MQ Advanced components. You might not want the advanced functionality or do not have the required license. For information on which components are included with the IBM MQ Advanced option, see IBM MQ Virtual System Pattern Type software components for Linux systems and IBM MQ Virtual System Pattern Type software components for AIX systems.