Comments (0)

Links:

http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzax.doc/mo10120_.htm

http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzax.doc/mo10390_.htm

More information will be added as and when i will get the time.

Comments (4)

Source: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzao.doc/mi10970_.htm

Configure your clients using attributes in a text file. These attributes can be overridden by environment variables or in other platform-specific ways.

You configure your WebSphere MQ clients using a text file, similar to the queue manager configuration file, qm.ini, used on UNIX platforms. The file contains a number of stanzas, each of which contains a number of lines of the format attribute-name=value.

In this documentation, this file is referred to as the WebSphere MQ client configuration file; its file name is generally mqclient.ini, but you can choose to give it another name. Configuration information in this file applies to all platforms, and to clients using the MQI, WebSphere MQ classes for Java, WebSphere MQ classes for JMS, WebSphere MQ classes for .NET, and XMS. Read more »

Comments (1)

Source: MQ Intercommunication.pdf

The channel auto-definition exit can be called on all platforms except z/OS when a request is received to start a receiver or server-connection channel but no channel definition exists. You can use it to modify the supplied default definition for an automatically defined receiver or server-connection channel, SYSTEM.AUTO.RECEIVER or SYSTEM.AUTO.SVRCON.

See next ‘Auto-definition of receiver and server-connection channels’ section for a description of how channel definitions can be created automatically.

The channel auto-definition exit can also be called when a request is received to start a cluster-sender channel. It can be called for cluster-sender and cluster-receiver channels to allow definition modification for this instance of the channel.

The channel auto-definition exit returns a response of either MQXCC_OK or MQXCC_SUPPRESS_FUNCTION. If neither of these is returned, the MCA continues processing as though MQXCC_SUPPRESS_FUNCTION were returned. That is, the auto-definition is abandoned, no new channel definition is created and the channel cannot start.

Auto-definition of receiver and server-connection channels

In WebSphere MQ on all platforms except z/OS, if there is no appropriate channel definition, then for a receiver or server-connection channel that has auto-definition enabled, a definition is created automatically. The definition is created using: Read more »

Comments (0)

In WebSphere MQ, there are three methods of providing security:

1. The Object Authority Manager (OAM)
2. User-written, or third party, channel exists
3. Channel security using Secure Sockets Layer (SSL)

The Object Authority Manager (OAM): This is automatically installed and enabled for each queue manager you create, unless you specify otherwise. All actions performed by an application connected to a queue manager are authenticated by the queue manager by a component called OAM. Every time an application attempts any action against a WebSphere MQ object, the OAM ensures that the identity under which that application is connected to QM has been set to allow the type of access it is requesting on the object. Read more »

Comments (4)

comments extracted from WebSphere MQ V7.0 Migration Information manual:

 Queue manager migration

Queue manager migration takes place when you upgrade WebSphere MQ by installing a new release or version.

When you upgrade a queue manager, resources it owns such as the current log files are automatically migrated for you.

  Read more »