|
EnvFile
|
The complete path of the file name to source to set the environment
prior to executing WebSphere MQ programs. Symantec recommends
storing the file on the shared disk. This ensures that the same file is available
on each failover node. Specifying this attribute is optional. The
shell environments supported are ksh, sh, and csh.
Type and dimension: string-scalar
Default: ""
Example: /MQ/setEnv.sh
|
|
MonitorProgram
|
Absolute path name of an external, user-supplied monitor executable. For information about setting this attribute:
Type and dimension: string-scalar
Default: ""
Example 1: /ibm/mq/myMonitor.sh
Example 2: /ibm/mq/myMonitor.sh arg1 arg2
|
|
SecondLevelMonitor
|
Used to enable second-level monitoring. Second-level monitoring is a deeper, more thorough state check of the WebSphere MQ Queue Manager. The numeric value specifies how often the monitoring routines must run. 0 means never run the second-level monitoring routines, 1 means run routines every monitor interval, 2 means run routines every second monitor interval, and so on.
Note: |
Exercise caution while setting SecondLevelMonitor to large numbers. For example, if the MonitorInterval is set to 60 seconds and the SecondLevelMonitor is set to 100, then the runmqsc command is executed every 100 minutes, which may not be as often as intended. For maximum flexibility, no upper limit is defined for SecondLevelMonitor. |
Note: |
The SecondLevelMonitor attribute is applicable to VCS versions earlier than VCS 5.1 SP1 with WebSphereMQ agent versions earlier than 5.1.9.0. From VCS version 5.1 SP1 with WebSphere MQ agent version 5.1.9.0 onwards, the SecondLevelMonitor attribute of the WebSphereMQ agent is deprecated. Instead, a resource type level attribute LevelTwoMonitorFreq should be used to specify the frequency of in-depth monitoring.
|
Type and dimension: integer-scalar
Default: 0
Example: 1
|
|
LevelTwoMonitorFreq
|
Specifies the frequency at which the agent for this resource type must
perform second-level or detailed monitoring. You can also override the
value of this attribute at the resource level.
The value indicates the number of monitor cycles after which the agent
will monitor the WebSphere MQ queue manager in detail. For example, the value 5 indicates that the
agent will monitor the WebSphere MQ queue manager in detail after every five online monitor intervals.
Note: |
This attribute is applicable to VCS version 5.1 SP1 with WebSphere MQ agent version 5.1.9.0 or later. If the VCS version is earlier than VCS 5.1 SP1 and the WebSphere MQ agent version is earlier than 5.1.9.0, the SecondLevelMonitor attribute should be used.
|
If you upgraded the VCS version to VCS 5.1 SP1 and the WebSphereMQ agent version to 5.1.9.0 (or later), and if you had enabled detail monitoring in the previous version, then do the following:
Type and dimension: integer-scalar
Default: 0
|
|
MonitorListener
|
Decides whether the monitor and clean function must monitor and clean the MQ listener process.
If this attribute is set to 1, the agent for WebSphere MQ
monitors and cleans the MQ listener process (runmqlsr), as part of mandatory processes.
If you set this attribute to 0 (default value), the agent
for WebSphere MQ does not monitor the runmqlsr process.
Note: |
If you enable MonitorListener, you should not configure separate resource for
listener process as this process is already monitored and cleaned as part of
WebSphereMQ resource. |
Type and dimension: boolean-scaler
Default: 0
Example: 1
|
|
MQInstallationPath
|
When more than one copy of WebSphere MQ is installed on a system, each Queue Manager is associated with a particular installation. Specify the location of the WebSphere MQ installation to which this Queue Manager is associated.
For WebSphere MQ versions earlier than 7.1, the default installation path is /opt/mqm or /usr/mqm for AIX platforms .
Specify a custom installation path for WebSphere MQ 7.1 or later.
If you change the installation that is associated with a Queue Manager, ensure that you update this attribute to specify the newly-associated installation path.
Example: /opt/customLocation
Default: " "
|
