Configuring WebSphere MQ

Configuring WebSphere MQ
Changing configuration information on Windows systems
Viewing configuration information
Changing configuration information on UNIX systems
Editing configuration files
When do you need to edit a configuration file?
Configuration file priorities
The WebSphere MQ configuration file, mqs.ini
Queue manager configuration files, qm.ini
Attributes for changing WebSphere MQ configuration information
All queue managers
Client exit path
Default queue manager
Exit properties
Log defaults for WebSphere MQ
Advanced Configuration and Power Interface (ACPI)
API exits
Queue managers
Changing queue manager configuration information
Installable services
Service components
Queue manager logs
Restricted mode
XA resource managers
Channels
LU62, NETBIOS, TCP, and SPX
Exit path
API exits
Queue manager error logs
Queue manager default bind type
WebSphere MQ security
Authority to administer WebSphere MQ
Managing the mqm group
Authority to work with WebSphere MQ objects
When security checks are made
How access control is implemented by WebSphere MQ
Identifying the user ID
Principals and groups
Windows security identifiers (SIDs)
Alternate-user authority
Context authority
Connecting to WebSphere MQ using Terminal Services
Creating and managing groups
Windows 2000
Creating a group and adding users
Displaying who is in a group
Removing a user from a group
Windows XP and Windows 2003
Creating a group
Adding a user to a group
Displaying who is in a group
Removing a user from a group
HP-UX
Creating a group
Adding a user to a group
Displaying who is in a group
Removing a user from a group
AIX
Creating a group
Adding a user to a group
Displaying who is in a group
Removing a user from a group
Solaris
Creating a group
Adding a user to a group
Displaying who is in a group
Removing a user from a group
Linux
Creating a group
Adding a user to a group
Displaying who is in a group
Removing a user from a group
Using the OAM to control access to objects
Giving access to a WebSphere MQ object
Examples of using the command
Using the command with a different authorization service
Using OAM generic profiles
Using wildcard characters
Profile priorities
Dumping profile settings
Displaying access settings
Changing and revoking access to a WebSphere MQ object
Preventing security access checks
Channel security
Protecting channel initiator definitions
Transmission queues
Channel exits
Protecting channels with SSL
How authorizations work
Authorizations for MQI calls
Authorizations for MQSC commands in escape PCFs
Authorizations for PCF commands
Guidelines for Windows 2000 and Windows 2003
When you get a 'group not found' error
When you have problems with WebSphere MQ and domain controllers
Windows 2000 domain with non-default, or Windows 2003 domain with default, security permissions
Configuring WebSphere MQ Services to run under a domain user
Applying security template files
Nested groups
Transactional support
Introducing units of work
Scenario 1: Queue manager performs the coordination
Database coordination
Restrictions
Switch load files
Configuring your system for database coordination
DB2 configuration
Checking the DB2 environment variable settings
Creating the DB2 switch load file
Adding resource manager configuration information for DB2
Changing DB2 configuration parameters
Oracle configuration
Checking the Oracle environment variable settings
Creating the Oracle switch load file
Adding resource manager configuration information for Oracle
Changing Oracle configuration parameters
Informix configuration
Ensuring Informix databases are created correctly
Checking the Informix environment variable settings
Creating the Informix switch load file
Adding resource manager configuration information for Informix
Sybase configuration
Checking the Sybase environment variable settings
Enabling Sybase XA support
Creating the Sybase switch load file
Adding resource manager configuration information for Sybase
Using multi-threaded programs with Sybase
Multiple database configurations
Security considerations
Administration tasks
In-doubt units of work
Displaying outstanding units of work with the dspmqtrn command
Resolving outstanding units of work with the rsvmqtrn command
Mixed outcomes and errors
Changing configuration information
XA dynamic registration
Error conditions
Summarizing XA calls
Scenario 2: Other software provides the coordination
External syncpoint coordination
The WebSphere MQ XA switch structure
Using CICS
The CICS two-phase commit process
Using the Microsoft Transaction Server (COM+)
The WebSphere MQ dead-letter queue handler
Invoking the DLQ handler
The sample DLQ handler, amqsdlq
The DLQ handler rules table
Control data
Rules (patterns and actions)
The pattern-matching keywords
The action keywords
Rules table conventions
How the rules table is processed
Ensuring that all DLQ messages are processed
An example DLQ handler rules table
Supporting the Microsoft Cluster Service (MSCS)
Introducing MSCS clusters
Setting up WebSphere MQ for MSCS clustering
Setup symmetry
MSCS security
Using multiple queue managers with MSCS
Cluster modes
Active/Passive mode
Active/Active mode
Creating a queue manager for use with MSCS
Creating a queue manager from a command prompt
Creating a queue manager using the WebSphere MQ Explorer
Moving a queue manager to MSCS storage
Putting a queue manager under MSCS control
Removing a queue manager from MSCS control
Taking a queue manager offline from MSCS
Returning a queue manager from MSCS storage
Hints and tips on using MSCS
Verifying that MSCS is working
Using the IBM MQSeries Service
Manual startup
MSCS and queue managers
Creating a matching queue manager on the other node
Default queue managers
Deleting a queue manager
Support for existing queue managers
Telling MSCS which queue managers to manage
Queue manager log files
Multiple queue managers
Always use MSCS to manage clusters
Working in Active/Active mode
PostOnlineCommand and PreOfflineCommand
Using preferred nodes
Performance benchmarking
WebSphere MQ MSCS support utility programs